update-item

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

No annotations provided, yet description fails to disclose mutation safety, idempotency, or return values. Critically omits account-tier restrictions visible in schema (paid/Enterprise-only features for 'snoozed' and 'teamId').

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?

Single sentence, front-loaded with action. Efficient though 'etc.' is vague given specific account restrictions exist in schema. Appropriate length for overview but misses opportunity to highlight critical constraints.

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?

Inadequate for a 9-parameter mutation tool with no output schema. Fails to address success/failure behavior, required permissions, or the fact that some parameters require paid/Enterprise accounts despite these being documented in the schema parameters.

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?

With 100% schema description coverage, baseline is 3. Description provides high-level categorization ('assignment' covering both user and team assignment) but adds no semantic depth beyond schema (e.g., explaining status lifecycle or snooze behavior).

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?

Clear verb ('Update') and resource ('item in Rollbar') with parenthetical examples of updatable fields. Distinguishes from sibling get/list tools by operation type, though could clarify distinction from get-item-details.

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?

Lists mutable attributes (status, level, title, assignment) but provides no guidance on when to use versus read-only alternatives or prerequisites like item existence. No mention of partial vs full update semantics.

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