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

Annotations already show readOnlyHint=true and destructiveHint=false. The description adds critical behavioral context: FREE businesses cannot use it, and access must be pre-verified via check_business_tool_access. This goes beyond the annotations and provides essential safety information.

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 contains four sentences, but some are repetitive (e.g., multiple conditions about access). It could be more concise by merging the access instructions. The structure is front-loaded with purpose but then shifts to detailed usage steps, which is acceptable but not optimized.

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 no output schema and many sibling tools, the description should explain what the return value looks like and how countTypes affects it. It also fails to mention that this tool likely returns a numeric count or breakdown. The description is incomplete for accurate agent usage.

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?

The input schema has two parameters with 0% description coverage. The description only mentions 'Get member counts' but does not explain what 'countTypes' means or how to use it. It also does not describe the required 'communityId'. This is a significant gap for the agent to correctly invoke the tool.

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 'Get member counts for a community' and clarifies that business/community are interchangeable. However, it does not specify what types of counts are returned (e.g., total, active) or distinguish from the sibling tool 'get_community_member_count'. Overall, the purpose is clear but slightly ambiguous.

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 strong preconditions: check permissions, call check_business_tool_access, handle grace-period warnings, never proceed when blocked. However, it does not differentiate from alternatives like 'count_business_members_with_filters' or 'get_community_member_count', leaving the agent to infer when to use this specific tool.

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