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

With annotations already declaring readOnlyHint/destructiveHint false and openWorldHint true, the description adds real behavioral context: newest-first ordering, the Inbox configuration requirement, and the auth requirement (Cotlet API key with app access). It still doesn't mention pagination behavior, so it isn't fully transparent.

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?

Content is front-loaded but repetitive: 'newest first' and 'booking reference' each appear twice across the first two sentences, and the title is restated. The duplication costs space without adding information.

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 list tool with no output schema, the description helpfully enumerates returned fields (guest name, booking reference, unread flag) and states preconditions and auth needs. Only pagination semantics are omitted, a minor gap given the cursor parameter.

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 limit, cursor, and unread_only are already documented. The description gestures at the unread concept but adds no syntax or format meaning beyond the schema, making the baseline 3 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?

States a specific verb and resource ('Lists Property Chat conversations') and distinguishes itself from the chat-detail sibling by pointing to get_chat via chat_id. Purpose is unambiguous, though the opening sentence repeats much of the title without adding scope.

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?

Gives a concrete prerequisite ('Property Chat must be switched on in Inbox first') and routes to the alternative tool for per-chat detail ('Pass chat_id to get_chat'). It lacks an explicit statement of when not to use this tool, but the routing and precondition are clear.

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