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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful content context — that each record bundles the latest message and linked reservation, and spans channels — plus the underlying Hostaway endpoint, but says nothing about pagination defaults, ordering, or result limits.

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 tight sentences, front-loaded with the core purpose, followed by the filter capability and the backing endpoint. No redundant restatement or padding.

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?

With no output schema, the description steps in to say what each returned conversation contains, which is the key thing an agent needs to decide relevance. It lacks pagination/ordering notes and explicit sibling routing, 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 four parameters are already documented in the schema. The description only reinforces reservationId ('Filter to one reservation') and says nothing about limit/offset/includeResources beyond what the schema states, 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 ('List guest conversations') and clarifies what a conversation is (unified inbox across channels) with its payload shape (latest message + linked reservation). This clearly distinguishes it from hostaway_list_conversation_messages, which would return the message thread rather than the conversation list.

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?

The description implies usage via 'Filter to one reservation' and the inbox framing, but never states when to choose this tool over hostaway_list_conversation_messages or hostaway_get_reservation. No when-not guidance or alternatives are named.

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