get_messages

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

With no annotations, the description carries the full burden, and it does disclose two useful facts: the GET method (implying a read-only, side-effect-free call) and the required `messages:read` permission. It says nothing about result ordering, total counts, or pagination envelope even though page/page_size exist, and 'Tags: Conversations' is metadata rather than behavior.

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?

Very short and skimmable, with the permission requirement front-loaded after the title. Some content is raw spec residue (the literal endpoint path and 'Tags: Conversations') that provides little decision value, but there is no verbosity to penalize.

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 5-parameter paginated, filterable listing tool with no annotations and no output schema, the description leaves too much open: return shape, ordering, and how this differs from sibling message-retrieval tools are all absent. The permission line is useful but insufficient on its own.

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 uuid, page, page_size, type, and private are all documented in the schema itself. The description adds no meaning beyond that—for example, no note on default sort order or how filters combine—so the baseline 3 applies.

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 gives the resource ('Messages') and the endpoint path GET /api/v1/conversations/{uuid}/messages, which together imply 'list messages in a conversation'. But 'Get Messages' largely restates the tool name, and it never distinguishes this listing tool from siblings like get_message, search_messages, or paginated_search_messages.

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?

There is no guidance on when to use this tool versus the sibling search/listing tools, nor any prerequisite or exclusion beyond the permission requirement. The agent must infer usage from the name and endpoint alone.

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