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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuine context beyond the schema by naming the channels messages come from (Airbnb, Booking.com, Vrbo, direct), but says nothing about pagination behavior, result volume, or permissions.

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 dense sentences with the core action and filter surface front-loaded; the trailing raw endpoint reference (Beds24: GET /bookings/messages) is low-value but brief. Little waste overall.

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 89% schema coverage and no output schema, the description covers the filter surface and message scope adequately. It could note the paginated response shape, but the page parameter description already handles that.

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 89%, so the schema already documents most parameters. The description restates the filter dimensions (booking, property, room, read/unread, source, age) but omits masterIds, messageIds and page, adding no syntax or format detail beyond the structured fields.

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 (read the guest conversation on bookings) and enumerates the message categories it returns (guest, host replies, internal notes, system). This clearly separates it from siblings like beds24_send_booking_message and beds24_mark_messages_read without opening any 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 description implies usage by listing filterable dimensions, but never states when to choose this tool versus alternatives such as beds24_get_booking or beds24_list_bookings. No exclusions or prerequisites are given, so the agent must infer context.

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