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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower; the description still adds real value by disclosing the cascade behavior (songs are preserved) and the permanence ('Cannot be undone'), neither of which is derivable from the annotations. It stops short of permission requirements or error/failure behavior, keeping it from a 5.

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 compact clauses, front-loaded with the destructive permanence, followed by the retention caveat and then the alternative. No filler, and the human-readable text is correctly labelled with the underlying DELETE /music/characters endpoint.

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 destructive singe-target delete with no output schema, the description covers irreversibility, side effects on dependent resources, and the nearest alternative — everything needed to call it safely. It does not indicate what the call returns on success, a minor gap in an otherwise complete definition.

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 both parameters documented in the schema (account, character_id), so the schema carries the burden and baseline 3 applies. The description adds nothing about parameter format or the multi-account case beyond what the schema already says.

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 ('Permanently delete') and resource ('one of your characters'), and immediately scopes the blast radius with 'songs already made with it are kept' — an agent can tell exactly what this does and does not affect. It also names the sibling it is not (mureka_set_character_private), which is strong differentiation in a long sibling list.

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?

Gives explicit routing: use this to delete, use mureka_set_character_private to merely hide it. The condition that selects each tool is stated outright, and the irreversibility warning tells the agent when extra caution is warranted.

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