mass_duplicate

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

With no annotations, the description carries the burden of behavioral disclosure, but it only states the operation without any consequences, safety notes, or effects on the original instance. It doesn't mention whether this is destructive, requires permissions, or how 'smart' behavior differs from regular duplication.

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 words. It front-loads the core action, though it sacrifices useful details for brevity, which is acceptable given the simplicity of the description 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?

The tool has a complex schema with nested operations and options, but the description fails to explain what 'smart' means, how multiple duplications are structured, or any edge cases. Without annotations or output schema, the description is insufficient for an agent to fully understand the tool's capabilities and constraints.

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 the 'duplications' parameter and its nested fields. The description adds no additional meaning beyond the name 'duplications' and the phrase 'at once', matching the baseline score of 3.

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 'Perform multiple smart duplications at once', which conveys the action (perform) and resource (smart duplications) while implying batch processing. This distinguishes it from the sibling tool 'smart_duplicate' by emphasizing 'multiple' and 'at once', though it doesn't elaborate on what 'smart' entails.

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 like 'smart_duplicate' or 'mass_create_objects'. It neither states explicit conditions nor exclusions, leaving the agent to infer usage solely from the tool name and the word 'multiple'.

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