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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds the ownership constraint, which is real context beyond the annotations, but says nothing about whether deletion is permanent, whether dependent scenes/clips are affected, or whether it fails vs. no-ops on an already-deleted id.

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?

A single front-loaded sentence with no filler or redundancy. Nothing could be removed without losing meaning.

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 one-parameter destructive tool whose annotations already carry the safety and idempotency profile and whose schema fully documents the id, this is close to sufficient. The remaining gap is downstream impact of deletion, which matters but is secondary given the structured fields already present.

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?

Only one parameter and schema description coverage is 100%, with the schema itself saying 'The studio_character id.' With full coverage the baseline of 3 applies; the description adds nothing about identifier format or where to obtain the id (e.g. from studio_character_list).

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?

Names a specific verb (delete) and a specific resource (studio_character), so an agent immediately knows what the tool does and can distinguish it from studio_character_create/read/update/list. It stops short of differentiating it from the many other destructive delete siblings, but the resource noun does that work.

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 phrase 'you own' implies an ownership precondition, which is useful implied usage guidance. However, there is no statement of when to use this versus studio_character_update (e.g. deactivate) and no exclusions or prerequisites spelled out explicitly.

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