delete_module

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

Annotations already flag destructiveHint and idempotentHint, but the description adds valuable context: it highlights that deletion is permanent, removes module associations, and explicitly states that underlying content is preserved. This goes beyond the annotation flags and clarifies the actual behavior.

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 extremely concise—two sentences, the first stating the action and the second delivering the critical caveat about content preservation. Every word carries weight, and the important warning is front-loaded.

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 the tool's simplicity (2 params, no output schema), the description covers the essential behavior: permanent deletion, impact on module associations, and non-deletion of underlying content. It provides enough information for an agent to use it correctly without over-explaining.

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 100%, with both parameters already described ('Module ID to delete' and 'Course code or Canvas ID'). The description adds no extra meaning about parameters or their formats, so it meets the baseline but does not enhance beyond 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?

The description states a specific verb and resource ('Delete a module from a course') and distinguishes from siblings like delete_module_item by explicitly clarifying that the module organization is removed but content is not. It also explains the scope of deletion (module and its item associations) precisely.

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 clearly implies when to use this tool (to delete a module) and indirectly differentiates from delete_module_item by noting that content is not deleted. However, it does not explicitly mention alternatives like delete_module_item for removing individual items, missing a direct when-not-to-use statement.

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