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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral context such as the synonym between business and community, access restrictions for FREE businesses, and the prerequisite tool call. This enhances understanding beyond annotations.

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 concise (5 sentences) and front-loaded with the purpose. Every sentence adds critical information: purpose, synonym, prerequisite checks, restrictions, and sequential instructions. No unnecessary words.

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?

The description covers permissions and usage flow well but omits return value information (no output schema) and does not explain pagination behavior implied by pageNo/pageSize parameters. For a listing tool, agents need to know the output structure and pagination details to use it effectively.

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 description coverage is 0% for 3 parameters, but the description does not explain any parameter (communityId, pageNo, pageSize). The agent must infer parameter meanings from the tool name and context, which is insufficient. The description fails to compensate for the lack of schema descriptions.

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?

Description clearly states the tool lists payouts for a managed community and clarifies that 'business' and 'community' are interchangeable. However, it does not explicitly differentiate from the sibling tool 'list_business_payouts' beyond the name, and lacks detail on payout types (e.g., pending, completed).

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 instructions: check business permissions first, FREE businesses cannot use this tool, call check_business_tool_access before collecting inputs, and show grace-period warnings and resubscribe link when blocked. This clearly defines when and how to use the tool.

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