voicebox_edit_story_item

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

No annotations are provided, so the description must disclose behavioral traits. It only lists actions without any information about side effects, destructiveness, idempotency, or required permissions. For a mutation tool with many parameters, this is insufficient.

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 sentences and front-loaded with the tool's purpose. It avoids extra words, though the second sentence is slightly redundant. It is efficient but could be trimmed.

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 9 parameters, an output schema, and complex action-dependent usage, the description is minimal. It does not explain how actions determine required parameters or provide usage patterns. The output schema exists, so return values aren't needed, but more usage guidance would improve completeness.

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 100%, so the schema already documents each parameter's purpose. The description adds no additional semantic meaning beyond the action list which is also in the schema's action enum. Therefore, it meets the baseline but doesn't exceed it.

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 edits a story item and lists five specific actions (trim, split, move, set volume, set version). It also explicitly calls it a combined tool for all item editing operations, distinguishing it from siblings like voicebox_add_story_item or voicebox_remove_story_item.

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 description implies this is the go-to tool for editing existing story items by calling it 'a combined tool for all item editing operations'. While it doesn't explicitly state when not to use it, the sibling tools list shows other tools for addition, removal, reordering, so the context makes the usage scope clear.

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