docs(guides): add type annotation best practices guide for function tools #786
+604
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Comprehensive guide addressing type annotation issues with Gemini API schema validation. This guide prevents the 3+ hour debugging cycles developers experience when using function tools with incomplete type annotations.
Problem Solved
Developers are hitting schema validation failures (400 Bad Request errors) when using function tools due to:
list/dictinstead ofList[T]/Dict[K,V]| Nonesyntax not supported (despite docs claiming it works)Real-world impact: Our team (DISC - MultiAgent RFQ Project) lost 3+ hours debugging this exact issue in production.
Related Issues (adk-python)
What This PR Adds
New Content (
docs/guides/tool-type-annotations.md- 580 lines)LiteralUpdates
docs/tools/function-tools.md: Warning calloutmkdocs.yml: Navigation entryTesting
mkdocs build --strictpassesImpact
Before: 3+ hours debugging, scattered workarounds
After: Clear patterns, prevent errors, reduce debugging time
Community Validation
Resolves: google/adk-python#3214
References: google/adk-python#1634, #2925, #2733, #398