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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds genuine domain context beyond that — existing videos retain the character, and future videos fall back to a faceless random narrator until another character is chosen. It does not state whether deletion is reversible or requires permissions, which keeps it out of 5 territory.

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 and immediately followed by consequences and the confirmation requirement; nothing is padding. The parenthetical about Cartoon Storytime is slightly noisy but conveys the fallback behavior concretely.

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 destructive tool with annotations covering the safety profile and no output schema, the definition covers the consequences of deletion and the user-confirmation requirement. The only real gap is the identifier format for character_id.

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 a single required parameter with 0% schema description coverage, so the description must compensate. The phrase 'if it was the one used in the videos' implies it identifies a specific existing character, but it never clarifies whether character_id is an ID, slug, or name — the schema leaves that open.

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 opens with a specific verb and resource ('Deletes a character'), which maps unambiguously to the tool name and clearly separates it from update_character, create_character, and delete_videos. It does not explicitly name a sibling as an alternative, but the operation 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?

'Confirm with the user first' gives a concrete precondition before invoking, and the downstream effects tell the agent when caution matters. It stops short of naming alternatives (e.g. update_character if the goal is only to modify), so it falls just below full when/when-not guidance.

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