update_entity_checklist_item

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

Annotations declare readOnlyHint=false and destructiveHint=false, and 'Edit' is consistent with that, so no contradiction. However, the description adds nothing beyond the annotations: no note on which fields are writable, what 'notify' triggers, whether changes are partially applied, or permission requirements.

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 zero waste. It is efficient, though arguably too terse for an 8-parameter mutation 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 an 8-parameter mutation with 13% schema coverage and no output schema, the description is far too thin. It omits field semantics, side effects (notify), and any behavior needed to invoke it correctly.

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 13% (only entityType is documented), and the description adds no meaning for the 8 parameters — text, checked, notify, assignee, deadline, itemId, entityId are all unexplained. With such low coverage the description should compensate but does not.

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 gives a clear verb (Edit) and resource (a single checklist item) scoped to projects/portfolios. It distinguishes itself implicitly from broader siblings like update_entity_checklist (whole checklist) and move/delete variants, though it does not name 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 indication of when to use this tool versus update_entity_checklist, add_entity_checklist_items, move_entity_checklist_item, or the sibling edit_checklist_item. The agent is left to infer selection entirely 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.