format_layout

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

Annotations indicate destructiveHint=true, and description confirms modification ('Apply'). Adds important limitation about Google Docs supporting only paragraph spacing, which goes beyond annotations.

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?

Two concise sentences with no redundancy. Front-loads purpose and key limitation. Efficient.

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?

Description covers high-level functionality and the Google Docs limitation, but lacks detail on parameters, return values, or usage examples. For a tool with 6 parameters and nested objects, more context would be beneficial.

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 has only 33% parameter descriptions (file_path and google_doc_id). Description does not elaborate on parameters like strict, paragraph_spacing, row_height, or cell_padding, leaving many partially documented.

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 the action (apply), resource (layout controls), and specific aspects (paragraph spacing, table row height, cell padding). It also distinguishes platform support (Google Docs only paragraph spacing).

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?

Description implies usage for layout formatting but does not explicitly state when to use vs alternatives or exclusions. No mention of when not to use or alternative tools.

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