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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower, and the description still adds real behavior: results are ordered most recent first, each entry carries the last message and its state, pending items mean booking requests awaiting an answer, and it requires a Cotlet API key with app access. It omits pagination/result limits, which is a minor gap.

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 resource and content, then ordering, then the semantic meaning of 'pending', then the send_message linkage and auth note. Sentences each carry distinct information, though the opening two sentences overlap somewhat in restating 'Inbox conversations'.

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 no-output-schema list tool this is fairly complete: it describes what comes back (last message + state), the ordering, the auth requirement, and what 'pending' means. The only missing element an agent might want is any result limit or pagination behavior.

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 the schema already documents filter (with enum and default) and booking_id fully. The description only gestures at filters ('same filters as the Inbox') without adding format or default detail beyond the schema, so 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 ('Lists') and resource ('Inbox conversations with campers') and adds the payload shape ('the last message and its state'), so an agent knows exactly what this returns. It is distinguishable from send_message and list_bookings by the inbox/conversation framing, though it does not name a competing list sibling directly.

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 implies usage context ('same filters as the Inbox', 'Pending conversations include booking requests waiting for your answer') and links forwarding to send_message via conversation_id, which is helpful routing. However there is no explicit when-to-use-vs-alternative statement (e.g., versus hipcamp_list_booking_requests) and no exclusions.

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