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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=false; the description goes beyond them with concrete retry semantics ('reuse the same idempotencyKey and payload on retry') and states that a successful creation receipt obviates a second metadata read. It doesn't cover permission/visibility effects or failure modes, so a 4 rather than a 5.

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?

Three tight sentences, front-loaded with the selection condition before the workflow and retry guidance. No filler, though the retry sentence is dense enough to warrant a second read.

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?

An output schema exists so return values need not be explained, and the description covers the create-then-populate workflow, retry behavior, and the receipt shortcut. The undocumented folderId/visibility parameters remain a minor gap for a 4-required-param tool.

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 50%; title and idempotencyKey are documented in the schema, while folderId (including its null variant) and visibility are not. The description reinforces idempotencyKey retry usage but adds nothing for folderId/visibility, so it neither fully compensates nor is empty.

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?

States a specific verb+resource ('Create a new empty sheet') and even bounds the scope ('only when requested or no existing destination applies'). It does not explicitly differentiate itself from near-siblings like sheets_duplicate or sheets_insert_records, so it stops short of a 5.

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?

Gives an explicit when-to-use condition ('only when requested or no existing destination applies') and then prescribes the follow-up workflow (use returned ID to add schema and records in the same execution). An agent can decide whether to reach for this tool versus reusing an existing sheet without inference.

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