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

With readOnlyHint=true already declaring the safe read profile, the description adds useful behavioral context: what is returned by default and which message states require an extra parameter. It does not cover pagination behavior or rate limits, which are minor gaps for a read-only list endpoint.

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 description is three compact sentences that front-load the core purpose, then add filtering behavior and the underlying endpoint. Every sentence carries useful information with no repetition or filler.

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 adequately explains the returned message fields and the default filtering behavior. Pagination details are left to the schema, which is acceptable given the 100% parameter description coverage.

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 input schema. The description elaborates on includeScheduledMessages and default filtering but adds little for conversationId, limit, or offset beyond the schema, matching the baseline for high schema coverage.

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 clearly states that it retrieves messages for one guest conversation and lists the returned fields (body, direction, channel/type, status, timestamps). It is easily distinguishable from siblings like hostaway_list_conversations and hostaway_send_message.

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 explains the default filter (only sent messages) and how to include scheduled, paused, or failed messages via includeScheduledMessages. It does not explicitly name alternatives or when not to use this tool, but the context is clear for an agent that already has a conversation id.

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