canvas_list_missing_submissions

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds meaningful selection context by defining exactly what is returned, but it does not disclose potential behaviors such as pagination, ordering, default course scope when no observee is provided, or whether the list is limited to currently enrolled courses.

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 short sentences with no filler. The primary purpose and scope are front-loaded, and the conditional usage requirement is delivered directly in the second sentence.

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 read-only list tool with only two optional-looking parameters and no output schema, the description covers the core purpose and the most important precondition. It is sufficient for an agent to decide whether to invoke it and to know that courseIds is required for observees.

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 50%: courseIds is documented as required when observeeId is set, and the description reinforces that. observeeId itself has no schema description, leaving only the phrase 'linked observee' to imply its meaning, so the description only partially compensates for the gap.

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 names a specific action and resource: 'List past-due unsubmitted assignments', and adds a scope qualifier ('for the user or a linked observee') that separates it from broader listing tools. It does not explicitly name sibling tools, so it stops short of full differentiation.

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 clearly signals when to use the tool: when the need is for past-due unsubmitted assignments. It also gives the key conditional requirement, 'For an observee, courseIds is required.' It does not explicitly contrast with alternatives like canvas_list_assignments or canvas_list_recent_submissions, so it lacks the strongest routing guidance.

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