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

The description discloses that the tool creates a new file and leaves the original unchanged, which is important behavioral information not present in the annotations. It also mandates asking the user, a procedural constraint. It does not describe failure modes or side effects beyond creation, but the annotations (readOnlyHint=false, destructiveHint=false) already indicate it's a mutating but non-destructive operation, and the description adds useful context on the new-file behavior.

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 compact and well-organized: it starts with the core action, provides the format mappings, notes the non-destructive nature, and ends with a critical usage instruction. Every sentence contributes meaningful information without redundancy or filler.

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 conversion tool, the description covers the essential behavior: what it converts, what the output is, and the prerequisite to ask the user. It does not explicitly state the return value, but the presence of an output schema (per context signals) likely covers that. Given the tool's simplicity and the existing schema coverage, the description is sufficiently complete.

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 schema provides 100% coverage for the single parameter 'file_id' with its description. The description does not add further semantic detail about the parameter itself, only explaining the conversion behavior. With complete schema coverage, a baseline of 3 is appropriate; no additional compensation is needed.

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's purpose: converting Office/PDF files to Google-native formats, with explicit format mappings. It distinguishes from siblings like create_document or upload_file by focusing on conversion, and the mapping to specific target formats leaves no ambiguity.

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 provides a clear usage context: when you need to convert an Office or PDF file to a Google-native format. It also includes an explicit 'ALWAYS ask the user before converting' instruction, which is a strong usage guideline. It does not explicitly mention when not to use or list alternatives, but the mappings and the safety requirement make the intended usage clear.

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