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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds ordering behavior ('newest first'), confirms each record carries your public response if one exists, and discloses the auth requirement (Cotlet API key with app access) — useful context beyond the structured fields.

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?

Three tight sentences, front-loaded with what is returned before the filtering nuance and the auth note. No filler, though the final auth sentence is slightly tangential to the core listing operation.

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 listing tool whose annotations carry the safety profile and with no output schema required, the description covers the returned fields, ordering, filtering semantics, and auth need. Nothing critical to correct invocation is missing.

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 baseline is 3. The description nonetheless adds meaning the schema lacks: the schema only says 'false: only reviews without your response' and never explains the omitted case, whereas the description clarifies that leaving 'responded' empty returns all reviews. That resolves a real ambiguity.

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 names the specific resource (camper reviews of your listings) and enumerates the returned fields (rating, text, date, your response), making scope unmistakable. An agent can distinguish this from the sibling hipcamp_respond_to_review (the write side) without opening either 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?

It gives actionable filtering guidance: 'Leave responded empty to get all of them, or set it to false to find reviews you have not answered.' That is clear when-to-use context, but it never names an alternative tool or states when not to use this one, so it stops short of a 5.

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