search_docs

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, description provides minimal behavioral context—only states it searches. Does not disclose read-only nature, rate limits, authentication requirements, or limitations like name-only search.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no fluff. Front-loaded with purpose. Could be more structured, but efficient and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 3 parameters, output schema presence, and many sibling tools, description is too minimal. Leaves ambiguity about search scope, page_size behavior, and differentiation from other search tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 33% (only user_google_email has schema description). Description implies 'query' is name but doesn't clarify format, regex, or pagination. Fails to compensate for missing parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states verb (search), resource (Google Docs), criterion (by name), and API (Drive API). Distinct from sibling tools like search_drive_files (broader) and list_docs_in_folder (listing vs. searching).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives such as search_drive_files or list_docs_in_folder. Lacks when/when-not context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.