complete_assignment

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

No annotations are provided, so the description carries full responsibility. It discloses two key behavioral traits: returns 'needs_input' when no payload is given, and attempts module item completion if no submission path exists. This provides useful context for the agent's decision-making.

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 concise, consisting of two sentences that immediately state the purpose and then detail key behavioral nuances. Every sentence adds value with no redundancy, and the structure is front-loaded with the primary verb and resource.

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?

While the description explains the conditional outcomes (needs_input and module completion), it does not cover how to provide submission payloads or what the output schema returns. Given the tool's complexity (6 parameters, conditional logic), the description is adequate but lacks completeness in guiding the agent on parameter usage and expected outcomes.

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 input schema has 6 parameters with no descriptions (0% coverage). The tool description does not explain any parameter's meaning, format, or how they relate to the submission process. The agent must rely solely on parameter names, which are vague (e.g., 'text_submission', 'url_submission').

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 'Complete or submit an assignment in Canvas' with a specific verb and resource. It distinguishes from siblings by describing conditional behaviors like needs_input response and module item completion, which are unique to this tool.

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 when one needs to complete an assignment, but it does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or alternative tools are mentioned, leaving the agent with limited guidance.

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