delete_module

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

Annotations indicate destructiveHint: true, and the description adds valuable context: the deletion is permanent, removes item associations, but does not delete the actual content (pages, assignments, etc.). This clarifies the behavioral scope beyond the annotation alone.

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: a one-line summary followed by a bullet-like list of parameters. Every sentence adds value, and the structure is easy to parse quickly.

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?

The description explains the permanent nature and the non-deletion of content, but it lacks information about permissions, potential side effects, error scenarios, or what the output schema contains. For a destructive action, more context about safety and outcomes would be appropriate.

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%, so the description must compensate. It briefly describes course_identifier as 'Course code or Canvas ID' and module_id as 'Module ID to delete', adding some context beyond the schema's anyOf type. However, it does not explain formats, constraints, or how to obtain these identifiers.

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 action ('Delete a module from a course') with a specific verb and resource. It distinguishes from sibling tools like delete_module_item and update_module by specifying that it removes the module and its item associations but not the actual content.

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 does not provide guidance on when to use this tool versus alternatives such as update_module or delete_module_item. It lacks explicit when-to-use, when-not-to-use, or prerequisites, leaving the agent without clear decision criteria.

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