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

Annotations already provide destructiveHint=true and idempotentHint=true, but the description adds valuable context: it specifies the exact deletion scope (record plus primary S3 object) and notes that restoration requires re-upload or regeneration. This goes beyond the annotations and clarifies consequences.

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 sentences with no redundant wording. The first sentence front-loads the primary action and scope; the second adds idempotency and recovery context. Every word earns its place.

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 single-parameter delete tool with annotations covering destructive/idempotent behavior and an output schema present, the description provides sufficient context: what is deleted, permanence, and recovery path. It lacks explicit permission or error info, but those are not critical for this simple operation.

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% and the parameter videoId is described as 'Rendered video id to delete'. The description reinforces that this id refers to a Tutorializer rendered-video record, but adds no new technical details. Baseline 3 is appropriate for high 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?

The description clearly states the verb 'Permanently delete' and the resource: 'one Tutorializer rendered-video record and its primary S3 object'. This is specific and distinguishes it from sibling delete_speech, which targets speech records. The resource is unambiguous.

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 this tool is for deleting rendered videos, and the sibling list includes delete_speech for speech. However, it does not explicitly state when to use this versus delete_speech or any other alternative. The idempotency note gives behavioral guidance but not selection guidance.

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