canvas_missing_submissions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the return data (missing submissions, due dates, etc.) and hints at a read-only operation ('Get'), but lacks details on permissions needed, rate limits, pagination, or error handling. For a tool with zero annotation coverage, this is a significant gap in transparency about how it behaves beyond basic output.

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 appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by a bulleted list of returns and a concluding emphasis. Every sentence adds value without redundancy. It could be slightly more structured by explicitly separating usage guidelines, but it's efficient overall.

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?

Given the complexity (a read operation with no parameters) and no annotations or output schema, the description is moderately complete. It covers the purpose and output details well, but lacks behavioral context like authentication needs or performance traits. For a tool in this context, it provides enough to understand what it does but not how it operates fully.

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?

The tool has 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to add parameter details, as there are none to document. It effectively compensates by explaining the output semantics, which is valuable given the lack of an output schema. This meets the baseline for zero parameters.

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's purpose: 'Get all missing submissions across courses' with a specific verb ('Get') and resource ('missing submissions'). It distinguishes from siblings like canvas_get_my_submission (which retrieves specific submissions) and canvas_assignment_list (which lists all assignments). However, it doesn't explicitly contrast with canvas_todo_list, which might overlap in functionality for tracking overdue work.

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 implies usage context with 'Critical for finding overdue work!' and lists what it returns, suggesting it's for identifying unsubmitted assignments. However, it doesn't explicitly state when to use this tool versus alternatives like canvas_todo_list or canvas_planner_items, nor does it provide exclusions or prerequisites. The guidance is present but not comprehensive.

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