amulen_delete_checklist_item

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the risky mutation profile is communicated structurally. The description adds nothing beyond that: it does not say the deletion is irreversible, whether there is any confirmation or recovery path, or what happens to item ordering/IDs afterwards.

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?

A single short sentence with the resource and action front-loaded and no filler words. It is efficient, though its brevity borders on under-specification for a destructive tool.

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 destructive, open-world mutation with no output schema and zero parameter documentation, the definition is too thin. An agent would need to know the slug hierarchy, failure modes (missing item/task), and whether the action is reversible before calling it safely.

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 four required parameters at 0% schema description coverage, the description carries the full explanatory burden and provides none of it. It does not explain the project/board/task slug hierarchy, where those slugs come from, or that item_id must be an existing checklist item within that task.

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 names a specific verb and resource ('Delete a checklist item from a task'), which lets an agent distinguish it from siblings such as amulen_update_checklist_item or amulen_add_checklist_items. It stops short of explicitly naming those alternatives, but the operation itself is unambiguous.

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?

There is no guidance on when to use this versus the update/add checklist-item siblings, no prerequisites stated (e.g. that the slugs must already resolve), and no mention of whether deletion is item-scoped or wipes the whole checklist. The agent must infer all usage conditions.

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