list_messages

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds genuinely useful behavior: results are ordered newest-first and offset pages backward from the newest page. It omits default/maximum page size and what happens on out-of-range offsets.

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 short sentences, zero filler, with the core action front-loaded. It is efficient, though the terse offset fragment leaves the reader to infer directionality details that a slightly fuller clause would have settled.

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 0% schema coverage, no output schema, and no annotations on parameter behavior, the description is the only place an agent could learn page size, message object shape, or ordering guarantees, and it supplies essentially none of that. Adequate for choosing the tool, insufficient for calling it correctly on the first try.

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 0% across all three parameters, so the description must carry the load and mostly does not. It only clarifies offset semantics (skips from the newest page); limit has no default, maximum, or units documented, and conversationId's source is left implicit.

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?

"List messages in a conversation" states a verb and resource, but it largely restates the tool name; the only added nuance is the conversation scoping. There is no differentiation from siblings like get_conversation or search_conversations, which an agent must infer on its own.

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 never says when to use this versus get_conversation, list_conversations, or search_conversations, nor any prerequisites about the conversation state. The only guidance is the implicit ordering note in the offset sentence, which is about pagination rather than tool selection.

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