object.duplicate

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

With no annotations, the description should disclose behavioral traits. 'Duplicate an object' implies copying but omits key details: whether the duplicate is linked, if it inherits transforms, or the effect of the 'offset' parameter. The schema suggests behaviors (e.g., 'linked' boolean) but the description adds no clarity.

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?

While extremely concise, the description is underspecified for a tool with multiple parameters and no other documentation. It sacrifices informativeness for brevity, resulting in poor structure.

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 4 parameters, zero annotations, and a large sibling set, the description is far from complete. It fails to address duplication behavior, parameter roles, or relationship to other object tools.

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 0%, yet the description does not explain any of the 4 parameters (name, linked, object, offset). It provides no additional meaning beyond the parameter titles in the schema.

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 an object' clearly states the action and resource, distinguishing it from siblings like 'object.create' which creates a new empty object. However, it doesn't specify that it duplicates an existing object, lacking precision.

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?

No usage guidelines provided. The description does not indicate when to use this tool over alternatives like 'object.create' or prerequisites (e.g., the source object must exist). Lacks any contextual guidance.

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