get_conversation

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

With no annotations provided, the description carries the burden. It states that the operation is a read ('Read') and that the response includes 'all messages,' which provides basic behavioral transparency. However, it does not disclose auth requirements, error handling, or response details beyond message inclusion.

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 description is a single, concise sentence that gets directly to the point. No unnecessary words or repetition. It front-loads the action and resource.

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?

The tool is relatively simple (two required parameters, no output schema), and the description covers the essential functionality. However, without an output schema, it would be helpful to describe the response format (e.g., ordering, fields of the messages) or error conditions. The description is minimally sufficient but not fully complete.

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. It mentions 'specific message conversation thread' but does not explain the roles of chat_id and school_id or their relationship. The parameter names are self-explanatory, but the description adds minimal semantic value beyond the schema.

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 clearly states a specific verb and resource: 'Read a specific message conversation thread with all messages.' This distinguishes it from sibling tools like list_conversations (which lists, not gets a single thread) and get_post (which gets a post, not a conversation).

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 word 'specific' implies this tool is for retrieving one conversation rather than listing all, but the description does not explicitly state when to use this over alternatives or provide exclusions. Usage is implied but not directly guided.

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