add_entity_checklist_items

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is known, but the description adds almost nothing beyond that. It doesn't explain whether a missing checklist is auto-created, what the notify flag triggers, or how duplicate items are handled — meaningful behavioral gaps for a write tool.

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?

One compact sentence with the resource front-loaded and no filler. It is efficient, though the brevity is partly what leaves the semantics underspecified.

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 4-parameter mutation tool with low schema coverage and no output schema needs far more than one sentence. Key facts — create-versus-append semantics, notify behavior, item field meanings — are absent, leaving the agent to guess before invoking.

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 only 25%, so the description must compensate, and it largely doesn't. It conveys the project/portfolio scope but says nothing about notify, about the per-item fields (checked, assignee, deadline), or about ordering/deduplication of appended items.

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+resource: creating a checklist or appending items to a project/portfolio checklist, which is more than a tautology. However, it does not distinguish this from the many checklist siblings (add_checklist_item, update_entity_checklist, update_entity_checklist_item), and it leaves the create-vs-append behavior ambiguous enough that an agent can't tell which path it will take.

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 when-to-use guidance, no mention of alternatives, and no conditions selecting this over add_checklist_item or update_entity_checklist. The only hint is the entityType field's scope note in the schema, not the description.

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