Workbooks Delete Shared Template

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds value beyond that by flagging that confirm=True is required even though the schema defaults it to false and does not list it as required — a genuine behavioral detail. It doesn't say what access is lost when the share is deleted, keeping it at a 4.

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 short sentences, the action and its confirm requirement front-loaded, with the ID-retrieval hint last. No wasted words.

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 2-parameter destructive tool with an output schema and full annotation coverage, the description supplies the required confirm semantics and the ID source. It omits any note about consequences of deletion, a minor gap given everything else is structured.

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 coverage is 0%, so the description carries the burden. It compensates by explaining that confirm must be true (clarifying a default-false, non-required boolean) and by pointing to the tool that yields share_id. That covers both parameters meaningfully, though it doesn't describe share_id format.

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 and resource ('Delete a template share') that is unambiguously distinct from the sibling workbooks_list_shared_templates and workbooks_accept_shared_template. An agent can tell exactly what this does without opening the schema.

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?

Explicitly names the prerequisite for finding the target ('Retrieve share IDs with workbooks_list_shared_templates') and states the confirm requirement, which is real routing guidance. It stops short of stating when-not-to-use or irreversibility warnings, so not a 5.

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