Search Docs

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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds that it uses the Drive API with a mimeType filter and returns a formatted list, but it does not elaborate on pagination behavior, auth requirements, or what 'formatted list' entails. With annotations covering the safety profile, the description adds only modest extra behavioral context.

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?

The description is two concise sentences, front-loaded with the core action, and contains no fluff or redundancy. It efficiently states what the tool does and what it returns.

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?

With three parameters, 0% schema description coverage, and an output schema present, the description is too thin. It explains the query as a name search but omits usage context for required parameters like user_google_email and does not specify how page_size affects results. This is insufficient for reliable tool invocation without external knowledge.

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 coverage is 0%, so the description must compensate for missing parameter explanations. It clarifies that 'query' is a name search, but it fails to explain 'page_size' and especially 'user_google_email' (a required parameter). This leaves the agent unsure how to populate essential inputs correctly.

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?

The description clearly states the tool searches for Google Docs by name using Drive API with a mimeType filter. This distinguishes it from broader file search (search_drive_files) and Gmail search, making its purpose unambiguous.

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?

The description implies the tool is for finding Google Docs specifically by name, providing clear context for when to use it. However, it does not explicitly mention alternatives or when not to use it, so it stops short of full exclusion guidance.

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