create-todo-checklist-item

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the mutation/safety profile is carried by structured data. The description still adds genuine context beyond that: it says the new item is returned with its id and that isChecked defaults to false. It does not surface the confirm-gate behavior, but that is documented in the schema's confirm parameter.

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?

It is front-loaded with the core action and then a compact tip covering body, defaults, return, and the alternative route. The opening 'Create a new checklistItem object' is slightly tautological, but the follow-up sentence earns its place.

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?

With no output schema, the description usefully states the tool returns the new item with its id, and covers body format, a default value, and the create-todo-task alternative. It is sufficiently complete for a create tool, with only minor gaps (e.g., the confirm gate and path-parameter sourcing) left to the schema.

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 83% (high), so baseline is 3. The description adds the concrete body shape { displayName: "..." } and notes isChecked is optional and defaults to false, but these meanings largely overlap with the schema's own field descriptions, so it adds only marginal value over structured data.

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 ('Create a new checklistItem object') and the tip clarifies that it 'Adds a step (checklist item) to an existing To Do task,' scoping it to an existing task. It also explicitly distinguishes itself from the sibling create-todo-task by naming that alternative. An agent can tell it apart from its siblings without opening a schema.

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 tip gives clear routing guidance: use create-todo-task with checklistItems when adding steps during task creation, implying this tool is for adding steps to an already-existing task. It does not state explicit prerequisites (e.g., that the task/list must exist and where the ids come from) or exclusions, but the alternative-tool condition is well covered.

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