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

Annotations already declare destructiveHint=true and idempotentHint=false, so the bar is lower; the description still adds useful context: permanence, no original-author-only restriction, account-level access requirement, and the deletedActivityId return plus not_found on repeat. The negative fragments ('No external publication or Scan launch') are weakly informative but do bound side effects.

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?

Front-loaded with the core action, which is good, but the trailing chain of negations ('Account access applies; no original-author-only restriction or board transition. No external publication or Scan launch.') reads like stacked discriminator fragments and dilutes the message without adding much.

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?

An output schema exists, so return-value explanation is not required, yet the description still names deletedActivityId and the not_found case. For a destructive three-param mutation the safety profile and eligibility constraints are adequately covered; only the absence of alternative-tool routing keeps it short of 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%, and each of the three required UUIDs is documented in the schema with a source tool hint. The description adds no formatting, sourcing, or constraint detail beyond the schema, so 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+resource ('Permanently delete one saved note') and immediately scopes it to 'this recommendation's note rows', which cleanly separates it from delete_recommendation_action and from the note create/update siblings. An agent knows exactly what is being deleted without opening the 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 eligibility context ('Only this recommendation's note rows are eligible; system events cannot be deleted') and the repeat-deletion behavior ('Repeated deletion returns not_found'), which tells the agent how to behave on retry. It does not name an alternative tool for cases where the note should be preserved or archived, so it stops short of explicit when-not routing.

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