ftrack_batch

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

No annotations are provided, so the description carries the full burden. It discloses the key behavior of atomicity (all succeed or all fail), which is essential. However, it does not describe the return value, ordering semantics, or potential side effects beyond the transaction guarantee.

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 that front-loads the core purpose and includes a clarifying parenthetical about transactional behavior. Every word earns its place without unnecessary elaboration.

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 operations array) and the absence of an output schema or annotations, the description is too sparse. It does not explain what the tool returns, how results are aggregated, or any practical constraints (e.g., maximum operations, error handling beyond rollback). This leaves important gaps for an agent to use it correctly.

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 all parameters and their purposes. The tool description adds no additional parameter-specific meaning, but that is acceptable given the schema completeness.

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 executes multiple operations in a single transaction, which is a specific verb+resource+scope. It distinguishes itself from sibling tools like ftrack_query or ftrack_create by emphasizing the batch/transactional nature.

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 when to use this tool: when multiple operations need to be executed atomically. It provides clear context about the transactional guarantee but does not explicitly mention alternatives or when not to use it, e.g., for a single operation, one would use the corresponding individual tool.

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