List Assignments

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

Annotations already state readOnlyHint=true and destructiveHint=false. The description adds that the results include due dates, points, and submission status, plus bucket filtering. However, it does not disclose behaviors like pagination, unpublished assignments, or rate limits, so value beyond annotations is moderate.

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 two sentences: the first clearly states the tool's purpose, and the second efficiently explains bucket usage. No wasted words, front-loaded with the main action.

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?

With strong annotations and an existing output schema, the description covers the core purpose and filter options. The main gap is not pointing to related tools like whats_due or get_assignment, which would help an agent choose correctly in ambiguous cases. Overall, it's nearly complete for a read-only list tool.

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%, so parameters are well-documented. The description adds meaning for bucket by describing its filtering purpose, but only lists a subset of allowed values (upcoming, overdue, unsubmitted, past) versus the full enum (which also includes undated, ungraded, future). This is a minor enrichment over the 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?

The description clearly states the tool lists a course's assignments with due dates, points, and submission status. This specific verb+resource+detail distinguishes it from siblings like get_assignment (single assignment), whats_due (due items), and my_submission (individual submission).

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 says to use bucket for filtering, but does not explicitly mention when to use this tool versus alternatives like whats_due or get_assignment. The context is implied by the purpose, but no exclusions or alternatives are named.

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