amulen_add_checklist_items

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the agent knows it is a non-destructive write. The description adds nothing beyond that — no mention of what happens on partial failure, whether items append or replace, ordering, duplicates, or whether the response returns created item IDs.

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?

Two sentences, action stated first, the parameter example immediately after. No filler and nothing repeated from the schema verbatim.

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 four-required-parameter mutation with no output schema and 0% schema coverage, the description leaves too much open: how slugs are obtained, whether the call returns the new items, and whether the task must be pre-existing. Only the items payload is adequately specified.

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, and it does partially: it spells out the items element shape (titulo required, descripcion optional) that the bare schema leaves as additionalProperties:string. However, the three required slug parameters are never explained, so a quarter of the surface remains undocumented.

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?

"Add one or more checklist items to a task" gives a specific verb (add) and resource (checklist items) plus scope (one or many, attached to a task). It implicitly distinguishes itself from the update/delete checklist siblings, though it never names them.

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 when-to-use guidance: nothing tells the agent to prefer this over amulen_update_checklist_item when an item already exists, and no prerequisites (task must exist, slugs must resolve) are stated. Usage is only inferable from the tool name.

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