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

Annotations indicate readOnlyHint=true and destructiveHint=false. The description adds important context: it is for managed communities, the tool requires permission checks, and FREE businesses are restricted. This goes beyond annotations by detailing access limitations and prerequisite steps.

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 reasonably concise, starting with the core purpose then adding usage guidelines. It is well-structured with actionable steps, though it could be slightly trimmed without losing essential 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?

Given the tool has 12 parameters, no output schema, and minimal annotations, the description is insufficient. It does not explain the return format, what the exported data looks like, or how to use the filters. This leaves significant gaps for an agent to correctly invoke the tool.

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 12 parameters with 0% description coverage, and the tool description mentions only 'manager member filters' without explaining any specific parameter's meaning. The description fails to compensate for the lack of schema descriptions, leaving the agent uninformed about how to set each parameter.

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 exports members for a managed community using filters. It clarifies that 'business' and 'community' are interchangeable, which helps avoid confusion. However, it does not explicitly differentiate from the sibling tool 'export_community_members', which might have a similar purpose.

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 guidance on when to use the tool: it requires checking business permissions, notes that FREE businesses cannot use it regardless of features, and instructs to call 'check_business_tool_access' before collecting inputs. It also mandates showing grace-period warnings and never proceeding when access is blocked.

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