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

readOnlyHint=true already covers the safety profile, and the description reinforces it consistently with 'Computes only — creates nothing'. Disclosing the underlying endpoint (POST /api/v3.3/quotes) is useful context given the POST verb despite read-only behavior. It does not say whether the quote is persisted, whether it expires, or what currency it returns.

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?

Two sentences, zero filler: the pricing breakdown and scope come first, the read-only constraint second. Every clause earns its place.

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?

There is no output schema, and the description compensates by enumerating the returned cost components (rent, fees, taxes, deposit, total) — a real gain. It stops short of currency, tax handling, or quote validity, which an agent pricing a stay might want, so it falls just short of fully 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?

Schema coverage is 100%, so all 8 parameters (including lead_uid, pet_count, agency_uid) are already documented in the schema. The description's 'for the given dates and party' only loosely gestures at check_in/check_out/guests and adds no format or default information beyond what the schema provides, so the 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 (price/quote) and resource (a prospective stay), and enumerates exactly what is computed: rent, fees, taxes, security deposit and total. 'Computes only — creates nothing' differentiates it from the write siblings (hostfully_create_lead, hostfully_create_job) without the agent needing to read any schema.

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?

Implied usage is clear — use it to price a prospective stay before booking — and 'creates nothing' implicitly warns against treating it as a booking path. However, no explicit when-not and no named alternative (e.g. hostfully_get_pricing_periods for raw rate periods, hostfully_create_lead for persisting a quote context), so routing is left to inference.

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