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

Annotations already indicate destructiveHint=true. The description adds that it requires a specific confirm value and permission checks (FREE businesses blocked, grace-period warnings). It discloses behavioral traits beyond annotations, though could more clearly state the effect of sending stress test messages.

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?

The description is relatively concise with 6 sentences. It front-loads the action and then provides prerequisites. Could be slightly more efficient, but no wasted sentences.

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?

Given 5 params, no output schema, and sibling tools (including send_magic_reach_message), the description covers the action, prerequisites, and permission checks. However, it does not explain what a stress test does differently, return value, or effects. Adequate but could be more 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 coverage is 0%, so description must explain parameters. It only explains the confirm parameter ('set to SEND_STRESS_TEST'). Other parameters (communityId, messageId, platform, numberOfRecipients) have no description meaning added beyond schema names. This is insufficient.

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 clearly states the action ('Send a Magic Reach stress test message'), verb and resource are specific. It distinguishes from siblings like 'send_magic_reach_message' by specifying 'stress test' and requiring confirm set to 'SEND_STRESS_TEST'.

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?

The description provides explicit when-to-use conditions: check business permissions, FREE businesses cannot use, call check_business_tool_access first, show warnings. It does not mention alternative tools for non-stress-test messages, but prerequisites are well covered.

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