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

Annotations only cover readOnlyHint/openWorldHint, and the description adds real operational context: 401 means an invalid/expired token, the list is deliberately unpaginated because upstream ``page`` is overloaded, soft-deleted rows shrink a page without being an error, and the payload is a bare array under ``data``. That is well beyond the annotations, though it stops short of describing ordering guarantees or rate 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?

Front-loads the stage and method, then splits the two modes into clearly labeled bullets, followed by quirks and error handling. Despite its length, nearly every sentence carries a distinct operational fact (unread flag, message_type semantics, soft-delete behavior, payload shape).

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 two-parameter read tool with an output schema, the description covers the remaining gaps an agent needs: mode selection, row fields, unread semantics, the pagination quirk, error handling, and the next tool to call. Nothing material is missing.

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 both parameters are already documented; baseline is 3. The description still adds meaning: it explains that ``thread`` should come from a list row to open one conversation, and that the upstream page parameter is intentionally withheld. It adds workflow context the schema alone does not convey.

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 (read) and resource (the owner's buyer/inquiry messages) and pins the lifecycle stage (post-publish) plus the underlying GET /messages. The two-mode structure (list vs. single thread) is spelled out, so an agent can distinguish it from siblings like beycome_reply_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?

Explicitly says when to omit ``thread`` (list ~20 recent conversations) versus when to pass it (drill into one full conversation using a thread value from a list row). It also routes the agent elsewhere for the follow-up action ('To answer a message, use beycome_reply_message') and names the re-auth path for 401s.

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