List Missing Submissions

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

Annotations already declare readOnly/idempotent/non-destructive, so 'Read-only' is largely redundant. What the description adds beyond them is genuinely useful: results span all courses in one call, and each item carries due date, points and overdue magnitude. Pagination/limit behavior of the result set is the notable omission.

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?

Three short sentences, front-loaded with purpose and followed by behavioral notes and the sibling disambiguation. Only waste is the 'Read-only' clause, which duplicates the readOnlyHint annotation.

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 zero-required-parameter read tool with no output schema, the description is nearly sufficient: it names the fields returned and the cross-course scope, which is what an agent needs to trust the result. A brief note on result volume/pagination would close the remaining gap.

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 'limit' is fully documented in-schema, so the description adds nothing about it — notably no hint about default page size or how to page through large result sets. Baseline 3 applies when the schema carries the parameter burden.

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?

Specific verb and resource ('List every assignment Canvas has flagged as missing') with an explicit scope ('across all your courses') and a statement of returned fields (due date, points, how overdue). It also names the sibling list_overdue_assignments and how it differs, so an agent can discriminate without opening schemas.

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?

It gives a clear selection rule: use this for a single cross-course sweep, and use list_overdue_assignments when you want per-course submission status. It doesn't state explicit exclusions (e.g. completed/graded submissions, unenrolled courses), so it falls short of a full when/when-not contract.

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