collections_items_update_items_live

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

No annotations are provided, so the description carries the full disclosure burden. It states 'update and publish existing items' but does not mention consequences like slug changes breaking links (only in schema), permission requirements, or reversibility. 'Directly to the live site' hints at permanence but lacks depth.

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 a single, concise sentence with no filler. It front-loads the action ('Update and publish') and includes the scope ('existing items... directly to the live site'), making it efficient and easy to parse.

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's complexity (nested request array, publish semantics, multiple sibling tools), the description is insufficient. It does not cover bulk update behavior, validation rules, return values, or the difference from draft-only updates. The schema provides some structure, but the description omits crucial operational 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?

The description adds no parameter-level meaning. It does not explain the 'request' structure, how to specify items to update, or the role of 'collection_id'. With schema description coverage at 50%, the description should compensate but fails to do so.

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 and publishes existing CMS items directly to the live site. It uses a specific verb and resource, distinguishing it from siblings like 'collections_items_update_items' (likely draft-only) and 'collections_items_publish_items' (publish without update).

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?

The phrase 'directly to the live site' implies immediate publication, but no explicit alternatives or when/when-not guidance is given. The description does not compare this tool to 'collections_items_update_items' or 'collections_items_publish_items', leaving the agent to infer the intended use case.

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