draw_winners

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

Discloses determinism and audit trail, which are key behavioral traits beyond the basic action. No contradictions. However, does not mention permissions or error conditions, but acceptable given no annotations.

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 concise sentences, front-loaded with purpose, no wasted words.

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?

Covers core purpose and behavior (determinism, audit, distinctness), but no output description, no parameter elaboration, and no error handling given lack of output schema and annotations. Adequate but leaves gaps.

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 has 0% description coverage; description does not individually explain parameters. Only implicit mapping: 'n' is number of winners, 'seed' is for determinism, 'snapshot_path' is the snapshot. Missing format or constraints.

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?

Describes specific verb 'draw' with resource 'winners from a snapshot', includes key attributes (deterministic, distinct). Distinguishable from sibling tools like winner_announcement or collect_entries.

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?

No explicit when-to-use or alternatives. The purpose is clear, but no guidance on when to avoid this tool vs other draw-related tools; relies on context.

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