Delete Recap

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, openWorldHint=true. The description adds a useful confirmation requirement ('requires confirm=true') and a required scope ('meeting_recaps:write'), which annotations don't capture. It doesn't describe irreversibility or what happens to associated data, so it's a small net addition.

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 compact sentences front-load the action and the required confirm flag. No wasted words, though the scope sentence is a bit parenthetical.

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 destructive, non-idempotent mutation tool with no output schema, the description should at least say what is deleted and whether the deletion can be undone. It covers confirmation and scope but leaves gaps in impact/irreversibility.

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 67% (recap_uuid lacks a description; account and confirm are documented). The description restates the confirm requirement but adds no new syntax/format detail beyond the schema. Baseline 3 for moderate 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?

States a specific verb+resource ('Delete Recap'), and the resource is clear from the name. It does not differentiate itself from sibling update_recap/get_recap/list_recaps, though the destructive nature is conveyed by 'Delete'. Adequate but no sibling differentiation.

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?

No when-to-use guidance. It does not say when to delete vs archive/update, nor preconditions for the operation. The only hint is the required confirm flag, but no user-facing context is given.

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