frontier_draws_status

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

With no annotations, the description carries the full burden and provides substantial behavior: it is a logical GET, it does not auto-fetch continuation pages, array responses are capped at 100 rows and 256 KiB, truncation is reported, and oversized records are refused without partial fields. This is strong operational transparency despite some boilerplate about 'required inputs' and 'other declared filters' that does not match 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?

The main purpose and key behaviors are front-loaded, but the description contains generic boilerplate sentences—'Required inputs reflect tool policy...' and 'Other declared filters are forwarded as supplied...'—that are confusing and largely irrelevant for a schema with one optional string and no additional properties. There is also a missing period after 'GET request'. It is somewhat over-built for its content.

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?

The tool is low-complexity and the description covers input scope, optional filtering, request behavior, and response limits. However, there is no output schema, and the description does not clarify what fields or structure the draw status response contains, leaving the agent to discover the return shape at runtime.

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 0%, and there is only one optional parameter, username. The description compensates by explaining that username is optional, acts as an explicit account-scoped selector when supplied, and that no account is assumed when omitted. This adds meaningful semantics beyond the parameter name and type.

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 opens with a specific verb and resource: 'Read the current and first-unclaimed frontier draw status.' This clearly identifies the operation and distinguishes it from ranked draw status tools, though it does not explicitly name sibling alternatives. The mention of 'current and first-unclaimed' adds useful scope beyond the bare tool name.

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 some context for the optional username parameter ('forwarded as an explicit account-scoped selector... no account is assumed') but never states when to choose this tool over siblings like frontier_draws_prize_overview or ranked_draws_status. There is no when-not-to-use guidance or explicit alternative routing, so the agent must infer usage from the name.

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