get_verified_stay_offer

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

Description adds verification detail (Ed25519 JWS against domain JWKS) and behavioral constraints (read-only, no locking/booking) beyond annotations which already indicate readOnlyHint and idempotentHint. No contradiction with annotations.

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 four sentences, front-loaded with the core action, and every sentence adds value. No redundant or filler text.

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?

Despite no output schema and 5 parameters, the description fully explains the tool's role in the workflow, the verification step, and the constraints. It provides enough context for an agent to select and invoke 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 already has 100% coverage with good descriptions. The description doesn't add significant new parameter semantics beyond contextualizing their role (e.g., domain is host-owned, dates exact). Baseline 3 is appropriate.

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 tool's action: 'Fetch, verify, and render a live host-domain signed VRP stay offer'. It distinguishes from siblings by specifying the context (after search, before quoting) and the read-only nature.

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?

Explicit guidance: 'Call after search returns a host domain, always before quoting final price or a booking link.' Also lists prohibitions: 'must not lock a quote, create a booking, collect guest details, or start checkout.' Clearly tells when and when not to use.

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