update_entity_checklist

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds genuinely useful behavior beyond that: item count is fixed and omitted optional fields are reset. This warns the agent about silent data loss, which the annotations do not convey. It stops short of noting permission needs or the effect of 'notify'.

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 that packs the key constraints into parentheticals with no filler. Dense and efficient, though it crams several distinct rules into one clause.

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 mutation tool with no output schema and thin schema coverage, it covers the highest-risk behaviors (fixed item count, field resets). The remaining gaps — notify semantics and return shape — are minor and not critical to invoking 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 coverage is only 25%, so the description must compensate. It clarifies that the whole item set must be supplied (count cannot change) and that optional fields reset if omitted, which maps meaning onto the items array, but it says nothing about notify or entityId beyond the project/portfolio phrasing.

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 ('Bulk-edit') and resource ('ALL checklist items of a project/portfolio'), and the emphasis on ALL implicitly separates it from update_entity_checklist_item. It does not name the sibling explicitly, so it lands short of a 5.

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?

Usage is only implied by the word 'Bulk-edit' and 'ALL checklist items' — an agent can infer this replaces the whole set rather than a single item. There is no explicit when-to-use/when-not guidance or reference to the sibling tools (update_entity_checklist_item, add_entity_checklist_items).

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