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

Beyond the readOnly/openWorld/non-destructive annotations, the description discloses ordering (soonest expiry first), the 24-hour expiry window, the expires_at field, and the API-key authorization requirement. These are substantial behavioral facts the annotations alone do not convey.

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 purpose is front-loaded in the first sentence and each subsequent sentence adds distinct value (ordering, expiry, follow-up tools, auth). It is slightly long but has no filler or redundancy.

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 having no output schema and only one optional parameter, the description explains the return content (dates, site, time left to respond, expires_at), the ordering, the expiry semantics, and the auth prerequisite. Nothing an agent needs to call this correctly 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% for the single optional listing_id parameter, so the schema already documents it fully. The description's mention of booking_id refers to downstream tools, not to this tool's parameters, and adds no syntax or format detail beyond the schema, so the baseline of 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?

The description states a specific verb and resource (lists booking requests) and narrows the scope precisely to pending requests the host has not accepted or declined. This cleanly distinguishes it from the sibling hipcamp_list_bookings, which would cover all bookings rather than only actionable pending requests.

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 says these are requests 'waiting for your answer' and that they are ones 'you have not accepted or declined', which gives clear context for when to call it. It also names the follow-up tools (get_booking, accept_booking_request, decline_booking_request) and the booking_id needed to invoke them, though it does not explicitly state when not to use this tool.

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