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

The annotations already indicate the operation is not read-only, but the description adds valuable behavioral context: it creates a new file, leaves the original unchanged, and requires user confirmation before conversion. This goes beyond what annotations alone provide.

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?

Every sentence earns its place: the format mapping, the side-effect clarification, and the critical user-consent requirement. The description is concise, scannable, and front-loaded with the primary action.

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?

For a simple one-parameter tool with an output schema, the description is complete. It covers what gets converted, the resulting formats, the side effect on the original file, and the required user interaction. No critical information for calling the tool correctly is missing.

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?

The input schema fully documents the only parameter (file_id) with a description, so the schema carries the semantic burden. The tool description does not add further detail about the parameter, but none is needed given 100% schema coverage.

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 and resource: converting Office or PDF files to the matching Google-native format. It lists concrete format mappings and distinguishes itself from create-related siblings by emphasizing conversion rather than creation.

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 gives clear context for when to use the tool: when an Office or PDF file needs to be converted to Google format. It also includes the important instruction to always ask the user before converting. It does not explicitly name alternative tools or state when not to use it, but the conversion use case is well-defined.

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