Read a conversation thread

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

Annotations already declare readOnlyHint=true and destructiveHint=false, confirming safe read-only behavior. The description adds valuable context beyond annotations by stating that the tool does not mark the conversation as read, a key behavioral nuance. This is sufficient disclosure for this type of tool.

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 just two sentences. The first sentence delivers the core action (read full thread), and the second adds a critical behavioral caveat. Every word is purposeful, and the information is front-loaded—no fluff or redundancy.

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 straightforward with one parameter and no output schema. The description adequately explains what it does and a key side effect. While it could elaborate on return format or ordering, annotations cover safety, and the complexity is low, making this description sufficiently 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 100%: the single parameter conversation_id has a clear description ('Conversation ID from canvas_list_inbox'). The tool description does not add additional meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 uses a specific verb-resource pair ('Read the full message thread') and clearly distinguishes the tool from siblings like canvas_list_inbox by specifying it targets a single conversation thread. The additional statement about not marking as read further clarifies its scope.

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 implies the tool is used after obtaining a conversation_id from canvas_list_inbox but does not explicitly state when to use it or when to prefer an alternative. No guidance on exclusions or alternative tools is provided, leaving the agent to infer context from sibling names.

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