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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It covers return fields, streak persistence, pot awards, jackpot requirements, costs, payment networks, auto-bridging, dynamic pricing, and where to read live values. This is exceptionally transparent for a financial transaction tool.

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 lengthy but each sentence adds meaningful information—streak rules, cost structure, payment networks, dynamic pricing, and prerequisite reads. It is dense rather than padded, but the lack of structured formatting and the embedded metadata tags make it slightly harder to scan.

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 tool is complex: multi-network payments, dynamic pricing, streak persistence, and contract-dependent jackpot targets. The description covers return values, costs, where to get live pricing, and dependencies on other tools. It omits error handling and response format details, but no output schema exists and the core operational context is well covered.

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 input schema covers 100% of parameters (ref and agentId) with descriptions, and the tool description does not add extra semantic meaning for these parameters. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 action ('Execute a coin flip') and the resource (Flipr.bet) with specific network details (Base mainnet, Solana mainnet, Chainlink VRF). This distinctly separates it from sibling tools that handle stats, pot, opportunity, or withdrawal operations.

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 tells users to check flipr_opportunity for ROI analysis before flipping and to read the jackpot target from flipr_pot or flipr_opportunity. It names alternatives and provides contextual prerequisites, though it does not explicitly state 'use this when you want to flip' since that is implied by the name.

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