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

Beyond the readOnly/idempotent annotations, the description discloses return contents, message ordering ('oldest first ... last element is the most recent'), read state, account info, lead details, and the needsFetch condition. This is substantial behavioral context that annotations alone do not provide.

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?

Four sentences, each earning its place: purpose, parameter source, return details and ordering, and conditional follow-up. The most important information is front-loaded, and there is no filler or repetition of schema contents.

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 single-parameter, read-only tool with no output schema, the description is thorough: it explains input provenance, output contents, message ordering, the needsFetch flag, and the exact sibling tools for refresh and ref-finding. Nothing critical for invoking it correctly is missing.

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 carries the full burden. It defines the single parameter's shape ('conversationRef { platform, id }') and, more importantly, tells the agent that refs come from campaignstack_list_inbox_conversations. That provenance adds meaning beyond the raw 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 opens with a specific verb and resource: 'Get a conversation with its full message history.' It clearly distinguishes this from list_inbox_conversations by emphasizing full history and names the source of the conversationRef, so an agent can tell it apart from sibling 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 explicitly tells the agent where to obtain the required parameter ('from campaignstack_list_inbox_conversations') and what to do when messages are not loaded ('Use campaignstack_refresh_inbox to populate them'). This gives clear context and names the relevant alternative tools.

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