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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the lower bar applies. The description still adds real context: access is gated by possession of the private organizer link (an authorization detail absent from annotations) and the output shape changes before versus after the draw. "Does not change the draw" does restate readOnlyHint, which is minor redundancy rather than contradiction.

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?

Three short sentences, front-loaded with the usage trigger, then the input, then the safety note. No filler and every clause carries information the agent needs.

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?

For a single-parameter read tool with full annotation coverage and an output schema, the description covers trigger, prerequisite, authorization model and a preview of returned content. Nothing required for correct invocation is missing, and listing return fields is mild redundancy rather than a gap.

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% and the single parameter's schema entry already explains that manage_url is the private organizer link containing /m/ and gives an example. "Takes the private organizer link" echoes the schema without adding format, validation, or failure-mode detail, so baseline 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 names a specific operation (retrieve the state of a draw) and enumerates exactly what is returned: entry count, names, commitment, and post-draw winners, backups and proof values. It also anchors the tool to its sibling create_prize_draw, so an agent can separate it from draw_winners and add_draw_entries without opening any schema.

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?

"Use this when the user wants the state of a draw made with create_prize_draw" gives a clear triggering condition and implies the prerequisite that the draw must already exist. It stops short of naming an explicit alternative or a when-not-to-use case (e.g. versus draw_winners for actually performing the draw), so it is strong but not exhaustive.

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