get_wallet_tickets

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'This does not move funds' largely restates structured data. The one genuinely additive detail is the scope limit to the active draw, but nothing is said about openWorldHint behavior (live chain read), failure modes for an invalid address, or rate limits.

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?

Two short sentences with the operation and scope front-loaded and no filler. The funds sentence is mildly redundant with readOnlyHint, keeping it just below top marks.

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 explained. However, the definition leaves 'active draw' undefined (presumably discoverable via get_jackpot) and gives no address format, which are the two things an agent needs to invoke this 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?

Schema description coverage is 0% for the single wallet_address parameter, so the description must compensate. 'Base wallet' implies an EVM-style address and the chain context, but no format, checksum, or validation expectations are given.

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 and resource ('Read a Base wallet's tickets') and scopes it to 'the active draw', which separates it from get_draw_history and check_wallet_prizes. It never names a sibling tool or says what it is not, so differentiation is inferred rather than stated.

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?

There is no guidance on when to call this versus check_wallet_prizes, get_draw_history, or prepare_ticket_purchase. The second sentence ('This does not move funds') is a safety reassurance, not a usage condition, so the agent must guess at the call context.

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