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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it merely restates the tool's action without adding detail. It does not indicate return format, whether search covers file content or metadata, authentication requirements, pagination, or any side effects.

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 exceptionally short and front-loaded, containing no filler or redundant words. While it is under-specified, the conciseness itself is effective; every word contributes to the core purpose, though it could be expanded without becoming verbose.

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 the lack of annotations, no output schema, and minimal parameter documentation, this description is incomplete. A search tool should elaborate on what is being searched (e.g., file names, contents), how results are returned, and how the 'type' filter affects behavior, but none of that is present.

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 0%, and the description provides no explanation of the 'q' or 'type' parameters. The schema only shows their types and an enum for 'type', but the description adds no meaning beyond that, so the agent must guess at query syntax and filter semantics.

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 a specific verb ('Search') and resource ('Google Drive files'), which distinguishes it from sibling tools like search_onedrive and read_drive_file. It is concise and unambiguous, though it does not mention the scope of the search (e.g., file names vs. content).

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 is provided on when to use this tool versus alternatives like search_onedrive or read_drive_file. There is no mention of use cases, exclusions, or prerequisites, leaving the agent to infer when this tool is appropriate.

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