Delete Recorder

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds context beyond annotations by specifying 'permanently delete' and confirming that 'existing recordings are preserved', which clarifies the non-destructive effect on recordings. No contradiction with 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?

The description is a single sentence, front-loaded with the core action and key side effect. No unnecessary words, earning its place with maximum efficiency.

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?

Given the tool's low complexity (one required parameter, simple delete action) and the presence of an output schema, the description provides sufficient information about the operation's scope and preservation behavior. No gaps for an agent to select and invoke correctly.

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 100% with a clear description for 'recorderId'. The tool description does not add additional meaning or usage notes for the parameter beyond what the schema already provides. Baseline 3 is appropriate.

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 uses a specific verb 'delete' and resource 'recorder/survey', states permanence and what is preserved ('Existing recordings are preserved'). This clearly distinguishes from sibling delete tools like 'delete_media' or 'delete_automation' by specifying the scope and side effect.

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 implies usage context (when you want to remove a recorder but keep recordings) but does not explicitly guide when to use this tool versus alternatives like 'delete_media' (for recordings) or 'get_recorder_info' (for inspection). No exclusions or comparisons provided.

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