ranked_draws_complete

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

With no annotations, the description carries the full burden, and it does so well: it discloses the 100-row and 256 KiB limit, explicit truncation notice, no auto-fetching of continuation pages, forwarding of filters without implied effectiveness, and refusal of oversized records without partial fields.

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 description is repetitive: the 100-row/256 KiB cap and truncation behavior are stated twice. It also contains grammar issues and a run-on sentence ('Makes one logical GET request Does not auto-fetch'), making it harder to parse than necessary.

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 zero-parameter read endpoint, the description covers the main invocation concerns: limits, truncation reporting, pagination behavior, and oversized-record handling. A minor gap is not explaining the shape of the returned verification data, but the low complexity and absence of an output schema make this acceptable.

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?

The input schema has zero parameters and 100% coverage, so the baseline is 4 and there are no parameters for the description to clarify. The reference to 'declared filters' is somewhat confusing given the empty schema, preventing a higher score.

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 object: 'Read completed ranked draws and their verification data.' This clearly identifies the resource and differentiates it from sibling tools like ranked_draws_status or ranked_draws_available_prizes, even without naming them.

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 explicit when-to-use guidance or mention of alternatives. The description gives operational caveats about pagination and truncation, but does not help an agent choose this tool over the many similar ranked_draws_* or frontier_draws_* siblings.

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