get_conversation_messages

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

With no annotations, the description carries the full behavioral burden. It discloses a fixed page size of 20 messages and that it returns both metadata and messages, but says nothing about permissions, error cases, or behavior for out-of-range pages.

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?

The core capability and pagination limit are front-loaded in the first sentence, and the arg list is compact. The final 'Returns...' line is somewhat redundant given an output schema exists.

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 present, the description covers the essential call-time facts: what it fetches, the fixed page size, and both parameters. The missing piece is routing guidance against its four siblings.

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%, so the description must compensate, and it does: it defines uuid as the Conversation UUID and page as a page number defaulting to 1, plus the non-schema fact that pages contain 20 messages. It could still clarify what happens when page exceeds the available range.

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 states a specific verb and resource ('Get full conversation content') and adds a scope detail (pagination, 20 per page), so an agent knows exactly what it retrieves. It does not, however, contrast itself with siblings like conversation_summary or browse_conversations, leaving differentiation to inference.

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 statement of when to use this tool versus the alternatives (browse_conversations, conversation_summary, search_history). The description only implies usage through its pagination note, and offers no prerequisites or exclusions.

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