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

Annotations already establish a safe, closed read (readOnlyHint true, openWorldHint false), so the description's job is to add depth, which it does: it explains what the proof consists of (slot, ticket total, Merkle root, drand round/randomness, winning ticket derivation) and discloses that a creator-awarded prize carries awardedBy: "creator" while an undrawn round has no proof. That output-variance disclosure is genuinely useful behavior an agent cannot get from the schema.

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 tight declaration whose most important element, 'one round in full,' is front-loaded, followed by the returned fields and then the two proof-variant caveats. Dense but every clause carries information; only the proof-field enumeration is slightly list-like.

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?

There is no output schema, so the description bears the full burden of describing return values, and it does so thoroughly, naming the round fields, the proof components, and the two conditional cases. An agent can call it and interpret the response correctly without further documentation.

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 coverage is 100%, with both mint (base58 mint address) and number (round number, minimum 1) documented in the schema itself. The description adds no format, range, or lookup semantics beyond what the schema provides, so the baseline of 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 states the specific resource fetched ('one round in full') and enumerates the exact contents: mode, target, pot, stateText, and the proof fields. It is clearly a single-round read, distinguishable from a plural listing, though it never names get_rounds or get_coin to sharpen the boundary.

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?

Usage is only implied: fetch this when you need a specific round's state and its proof, keyed by mint and number. There is no explicit statement of when to prefer it over get_rounds for a range, or when a round exists versus not, though the closing note about an undrawn round having no proof hints at an edge case.

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