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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=true, so the safety profile is covered. The description adds value beyond that: it explains the downstream consequence (flows stop emailing the address) and an auth requirement (owners/admins) that no annotation expresses. It omits reversibility/how to restore the recipient.

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, and the destructive effect is front-loaded ahead of the permission note. Every clause 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 one-parameter destructive removal with full schema coverage and annotations carrying the safety hints, the description covers effect and authorization adequately. The only meaningful gap is whether the removal is reversible or how the recipient would be restored.

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% and the single 'id' parameter is documented as coming from neuron_list_notify_recipients, which is where the routing value lies. The description adds no format or sourcing 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 (remove), a specific resource (outside address used for flow notifications), and the concrete effect ('flows can no longer email it'). It is clearly distinguishable from the neighboring add/list recipient tools by implication, but never names a sibling or scope boundary explicitly.

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?

'Owners and admins only' supplies a real permission prerequisite, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to the alternative (e.g. use neuron_add_notify_recipient to re-add, or neuron_list_notify_recipients to find the id). Usage is only implied.

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