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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description adds value by disclosing permission checks, business tier restrictions, and required UI flows (warnings, links). This goes beyond annotations but does not cover all behavioral aspects like pagination.

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 a single paragraph that front-loads the purpose, but includes procedural steps that could be streamlined. It is not overly long but lacks conciseness in explaining permissions and warnings.

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?

No output schema is provided, and the description does not describe the return value (e.g., list of opt-outs, fields). It also omits details about pagination, though parameters hint at it. Given the complexity of a list tool, the description is incomplete.

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 description coverage is 0%, and the description does not explain any of the 5 parameters (communityId, pageNo, sortBy, pageSize, sortOrder). With such low coverage, the description fails to compensate, leaving the agent without semantic understanding of inputs.

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 tool's purpose: 'List Magic Reach opt-outs for a managed community.' It specifies the resource (Magic Reach opt-outs) and the scope (managed community), distinguishing it from siblings like count_magic_reach_opt_outs.

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 prerequisites and prohibitions: check business permissions, FREE businesses cannot use, call check_business_tool_access before collecting inputs, show grace-period warning and resubscribe link, and never proceed when blocked. This fully guides 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.