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

Annotations already indicate read-only and non-destructive behavior. The description adds beyond that by disclosing that FREE businesses are blocked and that permission checks are required. However, it does not describe the return format or any side effects.

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 concise and front-loads the core purpose. It includes necessary usage instructions without excessive wordiness, though the note about interchangeability could be streamlined.

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 simple read tool with annotations, the description provides procedural completeness (permission checks, access blocks) but lacks details on parameter semantics and output structure (no output schema). This leaves gaps for the agent.

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 0% description coverage with two parameters (communityId, countTypes). The description only implies communityId's purpose via tool name. countTypes is completely unexplained, leaving the agent without guidance on valid values or semantics.

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 retrieves member counts for a community and clarifies that 'business' and 'community' are interchangeable. However, it does not explicitly differentiate from sibling tools like count_community_members_with_filters, which also deals with member counts.

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 instructions: check permissions, FREE businesses cannot use it, call check_business_tool_access before proceeding, and show warnings/links. This gives clear when-to-use and when-not-to-use guidance.

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