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

With no annotations, the description fully discloses the revenue-sharing mechanism, including quarterly allocation, score calculation, minimum balance rollover, payout requirements, forfeiture, and disclaimers. This provides comprehensive behavioral context.

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 core function is front-loaded in the first two sentences, but the remaining detailed terms are lengthy and could be condensed. The structure is clear but not optimally concise.

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 complexity of revenue sharing and no output schema, the description sufficiently explains what information the tool returns (payable/carried/paid amounts, payout details status) and the underlying rules, making it complete.

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 only parameter (token) is fully described in the schema as 'Your agent token from register_agent.' The description adds no additional semantics, so baseline 3 applies.

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 begins with 'Your revenue-share balance' and states it shows payable/carried/paid amounts and payout details status. This clearly identifies the tool's function and resource, and it is distinct from siblings like set_payout_details or get_leaderboard.

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 implies use for checking earnings but does not explicitly state when to use it versus alternatives like set_payout_details. No exclusions or prerequisites are mentioned.

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