delete_module_item

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

The description adds critical behavioral context beyond the destructiveHint annotation, clarifying that the mutation is a partial removal rather than a full deletion. This prevents misunderstanding about the tool's effect.

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 single-sentence purpose, a critical note, and a clear parameter list. Every sentence adds value with no redundancy.

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 covers the tool's core action, side effect, and parameter meanings. It omits prerequisites (e.g., permissions) and error handling, but given the existence of an output schema for return values and the tool's simplicity, it is largely sufficient.

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 provides brief but sufficient parameter explanations ('Course code or Canvas ID', 'Module ID containing the item', 'Item ID to remove'). While not exhaustive, these add meaning beyond the raw 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 clearly states the tool removes an item from a module, with the important nuance that it only unlinks and does not delete the underlying content. This distinguishes it from sibling tools like delete_module or delete_page.

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 explicitly highlights that the tool only unlinks, not deletes content, guiding the agent on appropriate use. However, it does not directly name alternative tools for full deletion, relying on the agent to infer from context.

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