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

Annotations indicate readOnlyHint=true and destructiveHint=false, which agree with listing behavior. The description adds context about permission checks and restrictions for FREE businesses, which are beyond annotations and helpful for safe usage. No contradictions. Could mention that segments are returned in a list form.

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 mixes purpose and usage guidelines. While it contains necessary information, it could be streamlined. The procedural instructions (e.g., 'Show any grace-period warning...') make it longer than needed. Purpose is front-loaded.

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 list tool with one parameter, the description covers purpose and usage constraints well. However, it omits parameter explanation and does not describe the output format (e.g., what fields each segment contains). Since no output schema exists, this missing information reduces completeness.

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 one required parameter, communityId, with no description coverage. The tool description does not explain what communityId expects (e.g., format, how to obtain it). With 0% schema coverage, the description should compensate but fails to add any parameter 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?

Clearly states the tool lists membership/member segments for a managed community. The verb 'list' and resource 'segments' are specific. However, it does not differentiate from sibling tool 'list_business_segments' despite clarifying that 'business' and 'community' are interchangeable.

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 explicit guidance on when to use: before offering or collecting inputs, check business permissions via check_business_tool_access. States that FREE businesses cannot use this tool regardless of feature rows. Informs about showing grace-period warnings and verified resubscribe links. This clearly defines both when and when-not to use, and names a prerequisite tool.

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