canvas_get_conversation

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

Annotations already declare readOnlyHint=true, and the description's verb 'Get' is consistent. The description adds the scope 'full thread with all messages', but it does not disclose other behavioral traits such as pagination, message ordering, or potential large payloads. It adds minimal value beyond annotations.

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, front-loaded sentence with no waste. Every word contributes to understanding the tool's purpose.

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 tool with one parameter and no output schema, the description should at least explain what the id is and what the response contains. It only states the high-level purpose, leaving essential usage details unaddressed. The presence of annotations reduces the burden slightly, but significant gaps remain.

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?

The input schema has one parameter 'id' with no description, and the description also provides no explanation of what the id refers to. With 0% schema description coverage, the description must compensate but fails to clarify even that it is the conversation ID. This leaves the agent guessing.

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 action ('Get') and the resource ('full Canvas conversation thread with all messages'), which distinguishes it from sibling 'canvas_list_conversations' that likely returns summaries. The scope 'full' and 'all messages' adds specificity.

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 this tool is for fetching a specific conversation thread in full, but it does not explicitly state when to use it over alternatives like canvas_list_conversations. No exclusions or alternative guidance is provided, though context makes the use case reasonably clear.

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