duplicate_spread

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

With no annotations, the description should disclose behavioral traits. It only states 'Duplicate a spread' without explaining whether content is copied, what happens to layers or positioning, or any side effects. The positioning parameter is mentioned in schema but not in the description.

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 short sentence, which is concise but arguably too terse. It contains no fluff, but lacks structure and important details that could be included without excessive length.

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 has 3 parameters, one with an enum, no output schema, and moderate complexity, the description fails to explain fundamental aspects like the duplication behavior, positioning options, or return value. It is incomplete for an agent to use correctly without additional 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?

Schema coverage is 67%, but the description adds no value beyond what the schema provides. It does not explain the meaning of parameters like 'position' or 'spreadIndex' in context. For example, it omits details on how the duplicate is placed relative to existing spreads.

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 'Duplicate a spread' clearly states the action and object, but does not distinguish from sibling tools like 'duplicate_master_spread' or 'duplicate_page', which operate on different entities. It is adequate but not specific about the scope (e.g., within the same document).

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 provides no guidance on when to use this tool versus alternatives such as 'move_spread' or 'duplicate_page'. There is no mention of prerequisites or context for duplication.

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