rentals_v3_by_role

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

With no annotations provided, the description carries the full burden and does an excellent job: it discloses no auto-paging, local truncation at 100 rows/256 KiB with truncation reported, refusal of oversized records, preservation of numeric strings and original fields, and measured vs unmeasured behavior (counterparty partial matching verified on player route only). This is far beyond typical descriptions and gives the agent accurate expectations.

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 information-rich, but it's a long block of text without clear structure or front-loading of the most critical facts. The core purpose is in the first sentence, but the rest reads as a stream of caveats. Every sentence earns its place, but the lack of structure hurts scannability for an agent.

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 read tool with no output schema and no annotations, the description is remarkably complete: it covers request behavior, limits, truncation, field preservation, and known measurement boundaries. An agent has enough to call it correctly and interpret results, including the caveat that unmeasured sort/status values may behave differently.

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 explains the required inputs (player, role, limit) and their policy/upstream significance, clarifies that limit is bounded 1-100, and warns that other declared filters are forwarded as supplied without implied effectiveness. It doesn't detail each optional parameter's meaning, but it provides enough context to use the required ones correctly.

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 states a specific verb and resource: 'Read public SPSP delegation rental records for an explicit player and borrower/lender role.' It also distinguishes itself from card-worker rentals and mentions the player route. However, it doesn't explicitly name a sibling alternative like rentals_v3_by_player, so it's clear but not fully differentiated from siblings.

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 context: it's for public SPSP delegation rentals, requires limit 1-100, makes one bounded GET with no automatic paging, and notes that other declared filters are forwarded as supplied without implied effectiveness. It doesn't explicitly say when not to use it or name alternatives, but the context is strong enough for an agent to select it appropriately.

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