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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is carried structurally. The description still earns credit by adding context beyond annotations: that the action is irreversible and that alert history is removed, which is exactly the consequence an agent should surface before calling.

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?

Two short sentences with zero filler; the destructive consequence is front-loaded right after the action statement so the agent sees risk before acting.

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 single-parameter mutation with annotation coverage and no output schema, the description supplies what matters: action, key, irreversibility, and what data is lost. It could optionally note error behavior for invalid IDs, but nothing essential is missing.

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 100% schema description coverage ('Monitor subscription ID to delete'), so the schema does the heavy lifting. The description adds only the phrase 'by monitor ID,' which does not extend meaning beyond the schema; 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?

The description names a specific verb+resource pair ('Stop monitoring a company and delete its subscription') and identifies the key ('by monitor ID'). An agent can distinguish this from siblings like monitor_subscribe and sanctions_unwatch without opening any 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?

Usage is implied by the verb — the agent knows this is the teardown counterpart to monitor_subscribe — but there is no explicit guidance on when to choose this over alternatives or what prerequisites (e.g., needing an existing monitor ID from monitor_list) apply.

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