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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that the export is for 'archived recipients' and produces 'CSV text', providing context beyond the annotations without contradiction.

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?

Three sentences, each value-adding: first states purpose, second and third deliver critical preconditions. No redundant words, front-loaded with key information.

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?

While usage guidelines are thorough, the description lacks parameter explanations and details about the CSV output (e.g., expected columns). Given the tool has no output schema and minimal schema coverage, this gap reduces completeness.

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?

Despite 0% schema description coverage, the description does not explain the meaning or format of the two required parameters (messageId, communityId). The agent must infer from the tool name or context, which is insufficient for reliable invocation.

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 'Export archived recipients for one Magic Reach message as CSV text', specifying the exact verb (export), resource (archived recipients), and output format (CSV text), distinguishing it from sibling tools like list_magic_reach_message_recipients that likely return structured data.

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?

Provides explicit step-by-step guidance: check business permissions, exclude FREE businesses, call check_business_tool_access before inputs, show grace-period warning and resubscribe link, and never proceed if blocked. This clearly tells the agent when and how to use the tool.

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