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

Annotations provide readOnlyHint=true and destructiveHint=false, confirming safe read operation. Description adds behavioral context: community managed by authenticated user, business permission requirements, and access-checking preconditions. No contradictions.

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?

Description is front-loaded with main purpose. Contains essential usage guidance, but could be slightly more concise by removing some procedural repetition (e.g., 'before offering this action or requesting its inputs' could be shortened). Still efficient overall.

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 provided; description does not indicate what fields are returned (e.g., list of zero links, pagination info). For a list tool, this is a significant gap. Parameters also unexplained, leaving agent with incomplete context for invocation.

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 has 6 parameters with 0% description coverage. Description does not explain any parameter meanings (e.g., pageNo, sortBy, status, pageSize, sortOrder) beyond implied communityId. With low schema coverage, description fails to compensate.

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 lists Zero Link products for a community managed by the authenticated user. The verb 'list' and resource 'zero links' are specific, but no explicit differentiation from sibling list tools like 'list_products' is provided.

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?

Excellent usage guidance: explicitly states prerequisite (check business permissions), constraint (FREE businesses cannot use), prerequisite tool (check_business_tool_access), and actions to handle access denial (grace-period warning, resubscribe link). Clearly distinguishes when and when not to use.

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