canvas_conversation

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

With no annotations, the description carries the full behavioral burden. It does disclose the return payload (complete messages plus attachments), which is useful beyond the schema, but it says nothing about whether access is restricted to the caller's own conversations, how very long conversations are paginated or truncated, or that the call is a pure read.

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?

A single compact line that front-loads the resource and appends the provenance constraint. No filler, though the extreme brevity leaves behavioral gaps that a slightly longer sentence could have closed.

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 one-parameter read tool with no output schema and no annotations, the description covers purpose and return content but leaves the safety profile (read-only nature), access scope, and handling of large conversations unstated. Adequate to invoke correctly, thin on behavioral context.

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% and the single parameter's schema description already states that the id comes from canvas_inbox. The description repeats that fact rather than adding format details, error behavior for an invalid id, or how the id relates to course context.

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 names a specific resource: the complete messages and attachments of a single conversation, and clearly distinguishes it from canvas_inbox, which supplies the conversation_id. The action verb is only implied (fetch/retrieve), but the scope is unambiguous.

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 parenthetical 'conversation_id 取自 canvas_inbox' gives an explicit prerequisite and ordering: call canvas_inbox first, then this tool with the returned id. There is no explicit when-not guidance, but for a one-parameter reader the routing information is sufficient.

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