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

Annotations already declare destructiveHint/openWorldHint/idempotentHint=false, but the description adds value beyond them: the member record is created if absent, group membership is deferred until confirmation, sending is throttled by the provider, and the underlying endpoint is named. It does not cover re-send behavior or what happens if the address is already confirmed, which keeps it from a 5.

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 critical signal ('WRITE, SENDS AN EMAIL'), then scope, alternative, and guardrail. Every sentence carries weight, though the parenthetical nesting in the first sentence makes it denser than ideal, and the trailing 'POST /members/optins' is marginal value for an agent.

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 14-parameter destructive send with a nested customFields object and no output schema, the description supplies the safety gating, the side effect on member creation, and the throttling caveat. Return-value expectations are the only real gap, and absent an output schema that gap is minor.

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 the baseline is 3, but the description goes beyond the schema by explaining the timing semantics of group_ids (joined only after confirmation) and the approval meaning behind confirm_send. That is genuine added meaning rather than restating field descriptions.

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 (sends an email), the resource (an opt-in confirmation request to a given address), and the side effect (person is added to groups only after confirming). It explicitly contrasts with cyberimpact_add_member, so the agent can distinguish it from siblings without opening schemas.

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?

Names the alternative explicitly ('Use this instead of cyberimpact_add_member when you do not have the person's consent yet') and gives the precondition for calling ('Only call it after the user has approved sending to this address, and set confirm_send to true'). Both the when and the when-not are covered.

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