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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does state the authentication requirement, which is useful, but it does not confirm read-only status, error behavior, rate limits, or what happens if both parameters are supplied or none are. These gaps leave the agent uncertain about side effects and edge cases, though the 'get' verb implies a safe read operation.

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 exactly two sentences: the first states the core purpose, and the second adds the parameter alternatives and authentication requirement. There is no filler, repetition, or tangential detail. The most important information is front-loaded, making it easy for an agent to quickly parse.

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 read operation with two optional parameters and no output schema, the description covers the essentials: what it does, the identifying inputs, and the auth requirement. It could be more complete by clarifying whether at least one parameter is required (schema says required: 0) and what the return structure is, but these are minor given the straightforward nature of the tool and that it returns 'full message history'.

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 coverage is 100% for both parameters, so the schema already documents their purpose and origin (e.g., 'Room name from list_conversations'). The description adds that the tool 'Accepts room_name or talent_slug', reinforcing that they are interchangeable alternatives, a nuance not explicitly in the schema. This is a modest addition, so a baseline of 3 is appropriate rather than a higher score for significant extra meaning.

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 operation ('Get full message history') with a specific resource ('a conversation') and scope, which immediately distinguishes it from siblings like list_conversations (listing conversations) and send_message (sending messages). The acceptance of room_name or talent_slug further clarifies the tool's targeted use.

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 indicates when to use it (retrieving full history of a single conversation) and imposes an authentication constraint ('Requires employer authentication'). However, it does not explicitly reference alternatives or when not to use it (e.g., when listing all conversations instead). The context is clear enough for most agents, but it lacks direct exclusion or sibling routing.

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