get_submission

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

No annotations provided, so description must fully convey behavioral traits. It implies a read operation and lists return fields, but does not disclose edge cases (e.g., no submission, errors) or authentication requirements. Minimal addition beyond basic action.

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?

Description is concise (about 5 lines) with structured Args and Returns sections. No redundant wording; every sentence adds value. Slight overhead from listing return fields, but overall efficient.

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 tool with two parameters and no output schema, the description explains it returns the user's own submission with feedback. It clarifies the scope ('your'). Lacks mention of error states or missing submissions, but overall covers essential context.

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?

With 0% schema description coverage, the description's Args section adds meaning: 'course_id: Canvas course ID' and 'assignment_id: Canvas assignment ID'. This provides basic context but lacks details on constraints or sources. Adequate but minimal.

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 "Get your submission for an assignment, including feedback and comments." It uses a specific verb and resource, and distinguishes from siblings like get_assignments (list) and get_assignment (details without submission).

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 explicit guidance on when to use vs. alternatives, such as when to use get_submission versus get_assignment or other sibling tools. The description does not mention prerequisites or exclusions.

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