canvas_get_assignment

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

With no annotations, the description carries the full disclosure burden. It usefully notes the plain-text rendering and the max_chars payload bound, and 'Get' implies a read operation, but it omits auth/permission requirements and error behavior (e.g., missing assignment or unauthorized course).

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?

Front-loads the core purpose in the first sentence, then lists parameters compactly in an Args block. No filler; every line supports invocation.

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?

An output schema exists, so return-value detail is not needed, and the max_chars bound is covered. However, for a no-annotation tool the description should also address read-only nature and failure modes, which it does not.

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 must compensate and largely does: it documents all three params, clarifies course_id falls back to CANVAS_DEFAULT_COURSE_ID, and explains max_chars=0 means the server default — semantics not present in 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?

States a specific verb+resource ('Get one assignment') and adds a distinct behavioral note that the description is rendered to plain text. The singular 'one' implicitly differentiates it from canvas_list_assignments, though no sibling is named explicitly.

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?

Usage is only implied: the required assignment_id signals it is for fetching a single known assignment. There is no explicit when-to-use vs when-not guidance, no mention of alternatives like canvas_list_assignments, and no prerequisites called out.

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