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

Annotations only declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: which fields come back, and the non-obvious default that only sent messages are returned unless includeScheduledMessages is set. It does not mention pagination behavior or ordering.

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 sentences plus an endpoint reference, with the returned payload front-loaded and the default-vs-opt-in behavior following. No redundant restatement of the tool name or title.

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 compensates by naming the returned fields and the default filtering behavior, and the schema handles pagination. Missing only minor operational detail such as ordering or result-size expectations for a single-conversation read.

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 all four parameters; baseline is 3. The description adds slight value by spelling out what includeScheduledMessages surfaces ('scheduled, paused or failed'), but says nothing about limit/offset semantics.

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 ('messages in one guest conversation') and enumerates the returned content (body, direction, channel type, send status, timestamps). The scope is clearly narrower than the sibling hostaway_list_conversations, so an agent can distinguish them 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?

The default filter behavior and the includeScheduledMessages escape hatch give conditional usage guidance for one parameter. However, there is no routing guidance relative to siblings (e.g., hostaway_list_conversations to discover an id, or hostaway_send_message to reply) and no stated prerequisites.

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