get_conversation

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely useful behavior: the cursor is bounded to the visible window, and opening the conversation may clear unread state. That unread-clearing side effect is real value the annotations don't convey, though return format and pagination behavior remain unstated.

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?

Three short sentences with little waste and the read purpose front-loaded, but the phrasing 'observed request/reply state' and 'does not accept requests' is terse to the point of ambiguity rather than dense with meaning.

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?

An output schema exists so return values needn't be described, and annotations cover the safety profile. However, for a 4-parameter tool with 0% schema coverage, the description leaves parameters and selection context unexplained, so it is only adequate.

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 four parameters. The description's mention of a 'cursor' loosely gestures at before_message_id, but account, conversation_id, and limit are never explained, and the cursor/window relationship is not clarified beyond what the schema already shows.

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 (Read) and resource (conversation context), but the scope-noun 'observed request/reply state' is opaque and the tool is not distinguished from close siblings like get_thread, get_inbox, or search_conversations. An agent can roughly tell it reads a conversation but not how it differs from those alternatives.

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?

No when-to-use guidance and no named alternative. The line 'Does not accept requests' hints at scope but is not a selection criterion, and nothing tells the agent when get_conversation should be preferred over get_thread or search_conversations.

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