ebay_clone_package

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

No annotations provided, and the description does not disclose behavioral traits such as what fields are duplicated, whether the operation is destructive or reversible, or any side effects. The phrase 'create a duplicate' is vague without additional context.

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 extremely short (6 words) but lacks necessary detail. Conciseness should not sacrifice clarity; here it is under-specified and fails to provide value beyond a tautology of the tool name.

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?

With many related package tools and no output schema, the description fails to explain what a 'package' is in this context, what the result looks like, or how it differs from other operations. It is not complete enough for effective tool selection.

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 0% and the description provides no explanation for the 'packageId' parameter. The agent has no way to know what value to provide or how it identifies the package to clone.

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 uses a specific verb 'clone' and resource 'package', clearly indicating it creates a duplicate. It distinguishes from sibling tools like 'create_package' or 'get_package' by using 'clone' rather than 'create', though it does not elaborate on what 'clone' 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?

No guidance on when to use this tool vs alternatives like 'create_package' or 'get_package'. The description does not specify context, prerequisites, or exclusions, making it difficult for an agent to decide appropriately.

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