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

Annotations provide minimal info (not read-only, not destructive). The description adds critical behavioral traits: confirm parameter requirement, free business restriction, need to check access, and conditionally proceeding with warnings. This goes well beyond annotations and prevents misuse.

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 of 6 sentences, front-loading purpose then guidelines. It is concise but could benefit from more structured format (e.g., bullet points for guidelines). Still, every sentence adds value with little waste.

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?

While access control and prerequisites are covered, the description lacks information about return values, parameter roles (e.g., latestTransactionId), and the overall payout creation process. Given no output schema and 0% parameter coverage, the description is incomplete for a tool of this complexity.

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 coverage is 0%, but the description only adds meaning for the 'confirm' parameter (must be CREATE_PAYOUT). It does not explain 'currency', 'communityId', or 'latestTransactionId'. Given 4 parameters with 3 required, the description fails to compensate for the missing 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?

The description clearly states the tool creates an on-demand payout for a community owner, with specific verb 'Create' and resource 'payout'. It distinguishes from sibling tool 'create_community_payout_on_demand' by clarifying that 'Business and community refer to the same thing and are interchangeable', avoiding confusion.

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 usage guidelines: requires confirm parameter set to CREATE_PAYOUT, check business permissions, FREE businesses cannot use, call check_business_tool_access before inputs, show warnings and verify resubscribe link, and never proceed when blocked. This gives clear when-to-use and prerequisites.

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