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

Annotations already flag readOnlyHint and non-destructive behavior, so the bar for extra disclosure is lower. The description adds that results are a 'bounded' page and lists the returned fields (subject, customer, assignee, tags, status, waiting time, timestamps), which goes beyond the schema. No contradiction with annotations.

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, front-loaded with the resource and fields, then the filtering purpose. No wasted words; the structure is clear.

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 lists the fields returned, which covers the 'what you get' aspect. It doesn't mention page size, ordering, or pagination mechanics, but the 'bounded page' and page parameter in the schema give enough to make a first call. Annotations cover safety, so this is adequate but not exhaustive.

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 only 43%, so the description bears a burden to explain params. It maps tag, inbox_id, status, and query to filters, and mentions 'account' though there's no account parameter, which is slightly confusing. The schema already covers _apiKey, query, and modified_since with descriptions, but the description doesn't clarify page or modified_since semantics, so compensation is partial.

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 names a specific verb ('Return'), a resource ('Help Scout conversation page'), and lists included fields. The second sentence clarifies the filtering purpose, distinguishing it from sibling tools like helpscout_get_conversation (single conversation) and helpscout_list_inboxes (just inboxes) without needing the 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 when looking for conversations matching account, status, inbox, tag, or search expression, but gives no explicit when-to-use vs alternatives. It doesn't name sibling tools like helpscout_get_conversation for single-conversation lookup, nor does it state when not to use this tool. This is implied rather than explicit guidance.

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