update_annotation_queue_item

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It reveals only that it updates status, but doesn't disclose whether it overwrites existing status, whether the item must exist, whether other fields are affected, or what the response contains. For a mutation tool, this is insufficient behavioral transparency.

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?

The description is two short sentences with no wasted words. It fronts the key purpose and includes the most important semantic detail (status values). While more information would be helpful, the description is appropriately concise for a simple tool, and every word 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?

Given the tool has four parameters, is a mutation, and has no annotations, the description is not complete. It lacks information about side effects, required privilege, return value (though an output schema exists), and the meaning of non-status parameters. The output schema might cover return values, but the description itself doesn't address the mutation's context.

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 0%, so the description is the only source of parameter meaning. It provides values for 'status' (PENDING or COMPLETED) but ignores 'queue_id', 'item_id', and 'project'. The other parameters are left to their self-explanatory names, which is not enough to understand the data model or constraints.

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 clearly states the tool updates a queue item's status and explicitly lists the allowed values (PENDING or COMPLETED). This is specific enough to distinguish it from sibling create/delete tools, though it doesn't explicitly differentiate from other update-like tools. The verb 'Update' and resource 'queue item's status' are precise.

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 guidance on when to use this tool versus alternatives. It implies usage for changing a queue item's status, but there are no explicit prerequisites, exclusions, or mention of alternative tools like create/delete. The context is minimally clear but lacks any comparative usage direction.

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