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 genuinely new context beyond that: the deletion is permanent and cascades to the charm's shared data, which the agent cannot infer from the annotations alone. It stops short of stating auth requirements or irreversibility confirmation steps.

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 tight sentence with no waste, front-loading the permanent nature of the operation and its cascade effect. 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 destructive two-parameter tool with full schema coverage and annotations carrying the safety profile, the description supplies the key missing piece (cascading permanent deletion of shared data). Only the absence of auth/prerequisite context keeps it from being fully complete.

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 description coverage is 100%, so both the slug and the optional agent_key (with its Authorization header fallback) are already fully documented in the schema. The description adds nothing about parameter formats or constraints, so the baseline 3 applies.

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 ('a charm you own') plus the scope of the effect ('and its shared data'). It is clearly distinguishable from siblings like update_app, remix_app, and browse_apps, though the terminology mismatch between 'charm' in the description and 'app' in the tool name/slug parameter adds minor friction.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternatives named. The word 'Permanently' implies the operation is irreversible, which is a useful cue, but the agent gets no help on prerequisites or on what to do instead if it only wants to modify an app (update_app).

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