canvas_deadlines

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

With no annotations, the description carries the full burden. It usefully discloses sort order (soonest first), the default window, and that submission status is included, but says nothing about auth requirements (a canvas_login sibling exists), pagination, or truncation limits for large course loads.

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 well-formed sentence with the resource list, window, and sort order front-loaded. No filler and nothing redundant.

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 one-optional-parameter read tool with an output schema, the description covers purpose, scope, ordering, and default adequately. Only auth/prerequisite context is absent, which is a minor gap given siblings like canvas_login exist.

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% and the single parameter is only typed as an integer with a default. The description supplies the actual semantics — the window in days — which the schema does not, though it merely restates the default value already present in 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?

States a precise resource set (assignments, quizzes, discussions) plus scope (due in the next `days` days) and ordering (soonest first). An agent can immediately tell this apart from canvas_announcements or canvas_courses without opening a schema.

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?

Usage is implied by the phrase 'due in the next `days` days (default 14)', which signals the upcoming-workflow context. However, there is no explicit when-to-use guidance, no when-not-to-use, and no sibling alternative named (e.g. vs canvas_courses for a full listing).

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