Get a rental quote

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

Adds substantial context beyond the annotations: the quote is free and non-binding, valid only 60 seconds, nothing is reserved or charged, and it requires AMPLERUN_API_KEY with the renter scope. It also discloses the return payload (raw API response plus fee_split, platform_fee_bps, host share). This is consistent with readOnlyHint=true since no state is mutated.

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?

Front-loaded with the core action and tightly packed, but the final sentences covering auth scope and return shape make it longer than strictly necessary for a quote call. Every sentence still carries information, so only minor trimming is possible.

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?

No output schema exists, yet the description explains the return shape (raw API response plus fee_split breakdown). Combined with the auth requirement and non-commitment guarantee, an agent has everything it needs to call this correctly.

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 100%, so every parameter is already documented. The description restates the budget_micro cap ('capped by budget_micro') and mentions offer/template sourcing, but adds no syntax or semantics beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb and resource ('Price a rental without committing: creates a free, non-binding AmpleRun quote') and immediately distinguishes itself from create_rental, which does the reserving. An agent can tell exactly what this does versus its 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?

Explicitly frames the call as optional ('this step is optional') and names create_rental as the alternative that quotes again when it reserves. The when-to-use relationship between the two tools is fully spelled out.

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