canvas_submissions

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

No annotations provided, so description is the sole source. It only states the listing function without disclosing behavioral traits like read-only nature, authentication requirements, pagination, or permissions. Minimal transparency beyond basic purpose.

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?

Single sentence is concise but lacks structure. Front-loaded with the verb and resource, but vague qualifiers like 'visible' reduce clarity. Could be improved without adding length.

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 no output schema and no annotations, the description is insufficient. It does not cover return format, pagination, error conditions, or example usage. For a listing endpoint, more context is needed for effective use.

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 0%, yet the description adds only vague context linking assignment_id to 'for an assignment' and course_id implicitly to the course. It does not explain the meaning of course_id, the behavior when assignment_id is null, or any constraints/formatting. Description fails to compensate for low schema coverage.

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?

Description clearly states tool lists submissions, either for a specific assignment or all visible course submissions. Verb 'list' and resource 'submissions' are specific. Differentiates two use cases based on assignment_id presence. However, 'visible course submissions' is ambiguous regarding what visibility criteria apply.

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?

No guidance on when to use this tool versus alternatives. Sibling tools like canvas_course_assignments deal with assignments, but there is no explicit exclusion or selection advice. Users must infer from context.

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