workspace_search_drive

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

Annotations already provide readOnlyHint and openWorldHint. Description adds no additional behavioral details such as pagination, sorting, rate limits, or error behavior. For a search tool, missing information on result format or iteration.

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, efficiently structured with key action and parameters. No redundancy.

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?

Despite complete schema coverage and annotations, the description is too sparse. For a tool with no output schema, it should explain return values, result format, or give query examples. Missing context for effective invocation.

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 100%, so schema already documents parameters thoroughly. Description does not add new meaning beyond what is in schema (e.g., no explanation of query syntax or MIME type formats). Baseline 3 is appropriate.

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 action (search), resource (Google Drive files), and method (query and MIME type filter). However, it does not differentiate from sibling tools like workspace_search_gmail, which also searches but for emails. The verb 'search' and resource 'Google Drive' are specific.

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 guidance on when to use this tool vs alternatives. No mention of preconditions, exclusions, or typical use cases. The existence of sibling search tools (e.g., workspace_search_gmail) is not addressed.

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