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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, but the description adds the details an agent actually needs before firing a destructive call: exactly what is destroyed (strip, description, voice binding), what survives (generations), and that the effect is permanent and irreversible. That is real added value beyond the structured hints.

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, front-loaded with the action, then the preservation rule, then the permanence warning as a one-word closer. Nothing is redundant and nothing buries the destructive nature of the call.

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 described. For a single-parameter destructive tool with strong annotation coverage, the description supplies the missing pieces: scope of destruction, what is preserved, and irreversibility. Nothing an agent needs to invoke it safely is absent.

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?

There is one required parameter, subject_id, with 0% schema description coverage, so the description carries the burden and does not fully meet it: it never says what identifier to pass or that it comes from list_subjects. It only names the entity being deleted, which is inferable from the tool name. Adequate but with a clear gap.

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 Subject") and immediately scopes it: the named identity goes, the generations it appeared in stay. That scope statement is what separates it from siblings like delete_generation or delete_storyboard, so an agent can route without opening a 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?

The blast-radius sentence implicitly tells the agent this is not the tool for removing a generation, and it clarifies what deletion does not affect. But it never names an alternative (delete_generation, update_subject) or states a precondition such as needing the subject to be unused or unshared, so usage is only implied.

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