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

With no annotations provided, the description fully carries the behavioral transparency burden. It discloses that the tool returns ETH balances for the 2-hour pot and jackpot, includes top streak holders, indicates time remaining, and clarifies the jackpot is target-based with targetStreak and roundId in the response. It also notes the response field is twoHourPot (not fourHourPot) and that the tool is FREE with rate limiting. This is thorough and prevents expected 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 slightly dense but every sentence contributes value: purpose, returned data, usage hint, jackpot explanation, field-name correction, and pricing/rate-limit note. The embedded pricing JSON adds some noise but is structured and relevant. No fluff or tautology.

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 there is no output schema, the description must explain what the tool returns, and it does so comprehensively: 2-hour pot and jackpot balances, top streak holders, time remaining, targetStreak, roundId, and the exact field name 'twoHourPot'. It also mentions the rate limit. For a zero-parameter read tool, this is complete enough for an agent to select and invoke correctly.

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 tool has zero parameters, so the input schema provides no meaning. The description goes beyond by explaining the output structure (twoHourPot, jackpot, targetStreak, roundId) which is helpful for understanding the tool's behavior. Baseline for 0 params is 4, and the description adds value by describing response fields rather than leaving the agent to guess.

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's function: 'Get current Flipr.bet pot balances and competition state.' It specifies the resource (Flipr.bet pots) and the action (get balances/state), and lists key outputs (2-hour pot, jackpot, top streak holders, time remaining). This distinguishes it from siblings like flipr_game_info or flipr_flip, which focus on other aspects.

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 explicitly says 'Use this to monitor pot balances,' providing clear guidance on when to invoke this tool. It doesn't name alternative tools or provide exclusion criteria, but the use case is well-defined. For a read-only tool with zero parameters, this is sufficient context.

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