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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-redundant behavior: no confirmation email, subscriber active immediately, and the returned subscriber_id. It still omits the key destructive detail for an upsert tool — whether existing props/firstname/lastname are merged or overwritten on an existing subscriber.

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?

Four dense sentences, front-loaded with operation type and resource, then permissions/consent, then side-effect (no confirmation email), then return value and endpoint. Nothing is redundant with the schema or annotations.

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 6-param tool with a nested props object and no output schema, the description covers operation type, consent prerequisite, tag convention, immediate activation, and the return field. The remaining gap is merge-vs-replace semantics on the update path, which matters given destructiveHint=true.

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 adds semantics the schema does not: the tag_ key prefix convention in props that turns a custom property into a tag. The example in the schema overlaps with this, but the naming convention as a mechanism is explained only here.

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 and resource ('subscribe an email address to a list') plus the upsert nuance ('or update it if it exists'), which is exactly what separates it from newsman_update_subscriber and newsman_unsubscribe_email. The 'WRITE:' prefix and the concrete endpoint make the operation type unambiguous.

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?

'Only use for people who gave consent' gives a real gating condition for when to call it, and the upsert wording tells the agent it need not pre-check existence with newsman_get_subscriber. However, no alternative is named for the case where the agent should explicitly update rather than subscribe.

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