get_assignment

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

No annotations are provided, so the description carries the full burden. It includes a representative return structure ({id, name, description, due_at, ...}) indicating a read operation, but lacks disclosure of authentication needs, error handling, or rate limits.

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 front-loaded with a clear one-line purpose, followed by Args and Returns sections. It is efficient and scannable, though the Returns section partly repeats the initial claim of 'full description and attachments'.

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 simple 2-parameter read tool, the description provides param descriptions and a return field sample. Given no output schema or annotations, this is adequate for an agent to understand usage, though error cases and performance implications are omitted.

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 0%, but the description explicitly defines both parameters ('course_id: Canvas course ID', 'assignment_id: Canvas assignment ID'), adding meaning beyond the schema's type and title. This compensates for the lack of schema descriptions, though more detail on expected formats could be given.

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 'Get a single assignment with full description and attachments,' specifying the action (get), resource (assignment), and scope (single). This distinguishes it from the sibling 'get_assignments' which would list multiple assignments.

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 implicitly indicates use when needing a specific assignment by ID, but does not explicitly state when to use this tool versus alternatives like 'get_assignments' or 'get_submission'. No when-not or contextual cues are given.

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