Bulk Update Stories

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

With no annotations, the description must disclose mutation behavior, but it only says 'update' without mentioning confirmation requirements (like the confirm parameter), partial failures, irreversibility, or side effects. The CONFIRM_WRITE requirement is hidden in the schema, not surfaced here.

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 one concise sentence, front-loaded with the primary purpose and zero redundancy. It is appropriately sized for a tool with this level of scope, though other dimensions carry the needed detail.

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?

This is a complex 16-parameter mutation tool with no output schema and no annotations. The description provides only a high-level purpose and omits essential operational details like the confirmation workflow, dry-run behavior, effect on existing fields, and error handling, making it incomplete for safe invocation.

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 44%, and the description does not enumerate any of the updatable fields beyond saying 'the fields to change on all of them.' It adds no detail about the nine undocumented parameters, so it fails to compensate for the schema gap.

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 (update), the resource (stories), and the scope (multiple at once), distinguishing it from single-story updates and other bulk operations like bulk_move_stories or bulk_delete_stories.

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?

It clearly indicates when to use this tool: when multiple stories need the same field changes. However, it does not explicitly mention alternatives such as update_story for a single story or exclusions for unsupported fields, so it falls short of a 5.

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