superchat_get_conversation

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds value by specifying the exact fields returned and the nuance that conversation status does not dictate the channel's messaging window. This is useful behavioral context beyond what annotations provide, though it doesn't mention error handling or return format, which are minor given the low complexity.

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 two sentences, front-loaded with the main purpose, and each sentence carries distinct value: the first states what the tool reads, the second gives a routing hint and a clarification. There is zero redundancy or filler. It is efficient and well-structured for quick comprehension.

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 simple get-by-ID tool with one parameter and no output schema, the description adequately covers what data is returned and clarifies a common misconception. It doesn't describe the exact JSON response structure, but that's not necessary for a read operation. It also mentions the message history alternative, which helps set expectations. Overall, the tool is well-specified for an agent to call it correctly.

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% and the parameter's description in the schema already explains the format and gives examples of where to obtain an ID. The tool description adds no additional meaning about the parameter beyond what the schema provides. Since the schema is thorough, the baseline of 3 applies; there is no need for the description to compensate.

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 the tool reads a single conversation thread and lists the specific fields it returns (contact, channel, inbox, status, and messaging time window). It distinguishes itself from siblings by explicitly naming list_conversation_messages for message history and clarifying the status/messaging window relationship, so an agent can tell it apart from related get/list tools.

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?

It provides an explicit alternative: 'Use list_conversation_messages for its message history when Enterprise access is enabled.' This tells the agent when not to use this tool for messages. It also clarifies a common misinterpretation about status vs. messaging window. It doesn't enumerate all possible alternative tools, but the most relevant one is covered, and the tool's purpose makes its own use case obvious.

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