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

Annotations declare destructiveHint=true and idempotentHint=true, but the description adds materially new behavior: dry-run-by-default, the shape of the preview (counts of messages/files/bytes), irreversibility with execute:true, that only Neuron's stored copy is touched (nothing removed from WhatsApp), and the 'Media removed' placeholder. This is genuine value beyond the structured fields.

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 tightly packed sentences that front-load the core action, then the scope caveat, then the safety-critical dry-run behavior. No filler.

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?

With no output schema, the description still explains what the dry run returns and the irreversible nature of the real run. Combined with annotations and a fully documented schema, an agent has everything needed to call it safely.

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%, so baseline is 3, but the description usefully reinforces the critical execute flag ('Pass execute: true to run it') and enumerates the media kinds covered. Minor mismatch: it says 'voice notes' where the enum uses 'audio' and omits 'sticker'.

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 precise verb+resource ('Remove media files... from chats') and immediately scopes it against the related sibling by clarifying that messages and captions are kept and only media goes. An agent can distinguish this from neuron_clear_chat without opening either 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?

Gives clear operational context: dry-run is the default and execute:true is needed to actually run it. It does not explicitly name neuron_clear_chat as the alternative for full-message clearing, so it stops short of the 5-level when/when-not routing.

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