check_wallet_prizes

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

The annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds only chain scoping ('Base wallet') and does not explain what a 'failed automatic prize payout' is, how a failure is determined, or what a positive result implies for recovery.

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?

A single front-loaded sentence with no filler or redundant restatement of the name. Its brevity is close to the limit of usefulness given the unexplained domain terminology.

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?

An output schema exists, so return values need not be described, and annotations cover safety. For a one-parameter read tool this is minimally adequate, but the agent is left unsure what constitutes an 'outstanding failed' payout or what action to take on a positive result.

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%, so the description must compensate for the single parameter. It only implies the address is a Base-chain wallet address, but gives no format expectation (0x hex, length) or validation behavior, leaving most parameter semantics undocumented.

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?

States a specific verb ('Check whether') and a specific resource ('outstanding failed automatic prize payout') scoped to a Base wallet, which is clearly distinct from sibling tools like get_wallet_tickets or get_jackpot. It loses a point only because 'failed automatic prize payout' is a domain term left unexplained.

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 gives no when-to-use or when-not-to-use guidance and names no alternatives, even though siblings such as get_wallet_tickets and get_jackpot cover adjacent wallet/prize queries. The agent must infer that this tool is for troubleshooting a missing payout.

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