Update Bundle

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

Annotations already signal destructiveHint=true and idempotentHint=true. The description adds 'partially update' which conveys a merge-like behavior, but it does not explain the confirm parameter or potential side effects (e.g., irreversible changes). It neither contradicts nor substantially extends the annotations, leaving some behavioral context to the schema.

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, direct sentence that is front-loaded with the verb and object. Every word contributes to the core purpose, with no redundant or vague filler.

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?

The tool has a complex nested spec with over 20 fields, a confirmation flag, and no output schema. The description fails to provide enough context for safe and correct invocation—spec construction, confirmation semantics, or what happens on destructive actions. It is too sparse for the tool's complexity.

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 0% schema description coverage, the description does not explain any of the top-level parameters. The nested 'spec' object's many fields are unmentioned except for a vague high-level summary. Critically, the 'confirm' boolean (default false) is not clarified, and the format for partial updates is left entirely to the schema.

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 verb ('partially update') and the resource ('bundle'), specifying the scope via 'details, layout, sorting, or display settings.' This distinguishes it from sibling bundle operations like delete or set_archived and from updates to other entities.

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 is provided on when to use this tool versus alternatives such as set_bundle_archived, configure_kanban, or even create_bundle. The phrase 'partially update' implies a subset of bundle modification capabilities but does not explicitly contrast with other update operations or mention prerequisites or confirmation flows.

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