rental_bids_by_player

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

With no annotations provided, the description carries the full burden, and it is unusually candid: it discloses no automatic paging, one logical GET, truncation at 100 rows/256 KiB, refusal of oversized records, preservation of numeric strings and original fields, and a specific caveat about not inferring filled state from numeric offer status. This far exceeds what is normally disclosed and materially helps an agent predict behavior.

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 dense and front-loaded with the core purpose, followed by important behavioral caveats. However, it is not concise: the phrase 'Two pages of two matched four rows; amount asc/desc changed the observed ordering' is cryptic and unexplained, and sentences like 'Required inputs reflect tool policy as well as measured upstream requirements' add vagueness rather than clarity. Most sentences earn their place, but the overall length and awkward phrasing cost it a higher score.

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?

Given no annotations and no output schema, the description covers a great deal: required inputs, limits, paging behavior, truncation, data preservation, filter caveats, and status interpretation. The main gaps are the lack of explicit semantics for sort, order, and offset, and the absence of any response-shape description beyond preservation/truncation notes. It is substantially more complete than most definitions but not fully self-sufficient.

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 description coverage is 0%, so the description must compensate. It does document limit (1-100), player (explicit), and gives a status caveat, plus an observed note about amount asc/desc affecting ordering. However, offset is not explained, sort/order valid values are only hinted at, and the statement that 'other declared filters are forwarded as supplied; their effectiveness is not implied' leaves real ambiguity about whether optional parameters actually work.

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 clearly states the operation: 'Read public SPSP delegation bids for an explicit player.' It names the exact resource and scope, and adds a useful exclusion: 'These are token delegations, not card-worker rentals,' which helps separate it from rental-focused siblings. This is a specific verb+resource definition with strong differentiation.

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 clear usage context: a bounded single GET with no automatic paging, a required limit of 1-100, and a required explicit player. It also warns that these are token delegations rather than card-worker rentals, which steers an agent away from the wrong sibling. It does not explicitly name alternative tools for when this one should not be used, so it stops short of full when/when-not guidance.

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