rental_offers_lowest_price

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

With no annotations, the description carries full burden and excels. It discloses exact response limits (100 rows, 256 KiB), truncation reporting, refusal of oversized records, no auto-fetch of continuation pages, preservation of price strings, and lacks inference. This is exceptionally transparent and beyond typical descriptions.

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 covers many behavioral specifics, but every sentence adds meaningful information. It is front-loaded with the main purpose and then details limitations. While not terse, it avoids redundancy and earns its length.

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-only endpoint with no output schema and no annotations, the description covers crucial operational details (limitations, truncation, refusal policy). It does not describe the full response structure, but it highlights key fields like price string. Given the tool's simplicity (zero parameters), the description is adequately complete.

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 schema has zero parameters, so the baseline is 4, but the description mentions 'Required inputs' and 'declared filters' which could mislead an agent into thinking parameters exist. It does not clarify that the input schema accepts no properties, creating ambiguity. This reduces value; the description does not add meaning beyond the empty schema and may cause confusion.

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 resource ('public V3 delegation rental offers lowest-price endpoint') with a specific verb ('Read'). It distinguishes from siblings by naming 'lowest-price' and 'V3 delegation', which is enough to differentiate from tools like rental_offers or rental_bids_lowest_price.

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 implies usage by stating what it does not do (no unit conversion, annualization, quote execution, or inference), which suggests using this only for raw lowest-price data. However, it does not explicitly name alternatives or provide when/when-not conditions, leaving the agent to infer from the purpose.

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