todo_add_checklist_item

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the agent knows this is a non-destructive write to an external system. The description adds nothing beyond that: it doesn't say whether the item is appended at the end of the checklist, whether ordering matters, whether duplicates are allowed, what happens if task_id is invalid, or what is returned.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes partly from omitting information rather than from tightening prose.

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?

A three-required-parameter mutation tool with zero schema description coverage, no output schema, and a bare one-line description leaves real gaps: ID formats, append semantics, error behavior, and return value are all unstated. Annotations cover only the safety profile.

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% and none of the three required parameters (list_ref, task_id, text) are described in the schema. The description only implies that text is the item content and that a task is targeted; it never explains the list_ref vs task_id distinction, accepted ID formats, or limits on text.

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?

States a specific verb ("Add") and resource ("checklist (sub-step) item to a To Do task"), and the parenthetical clarifies what a checklist item is. This distinguishes it implicitly from todo_update_checklist_item and todo_delete_checklist_item in the sibling list, 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?

No guidance on when to use this versus todo_update_task, todo_update_checklist_item, or todo_create_task. An agent must infer prerequisites (an existing task must exist, list_ref/task_id must resolve) and there are no exclusions or alternatives offered.

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