list_assignments

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the key trait — this is a read operation ('Read') — but says nothing about what 'assignment metadata' includes, how the bucket filter behaves, pagination, or authorization requirements. The core safety profile is clear, but other behavioral details are absent.

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 front-loaded sentence with the core action first and no filler. It is efficient, though the compressed jargon 'Canvas assignment bucket' trades clarity for brevity, and 'numeric' adds marginal value given course_id is typed as a string in the schema.

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 tool with no output schema and no annotations, the description defines the basic call adequately. But it leaves bucket semantics undefined, doesn't characterize the return contents beyond 'metadata,' and fails to position the tool against upcoming/overdue, which may be overlapping views. Serviceable with clear gaps.

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%, so the description must compensate. It adds real meaning for course_id (identifies the course being read, expected to be numeric). But bucket is glossed as 'Canvas assignment bucket,' which largely restates the parameter name without explaining accepted values or filtering behavior — a significant gap given the schema provides no descriptions.

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 ('Read'), resource ('assignment metadata'), and scope ('one numeric course ID'), which distinguishes it from siblings like list_courses (course list) and upcoming/overdue (time-filtered views). However, 'optional Canvas assignment bucket' is cryptic — an agent cannot tell what a bucket is or what values it takes, so part of the intended behavior remains unclear.

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 phrase 'Read one numeric course ID's assignment metadata' implies when to use it — when you need assignments for a single course — and the sibling tool names provide some contrast. But the description never explicitly says when not to use it or names alternatives such as upcoming/overdue for time-filtered assignment views, so the guidance is implied rather than stated.

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