ebay_create_package

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Create', implying mutation, but fails to mention required permissions, idempotency, side effects (e.g., impact on orders or shipments), or any constraints. The agent is left uninformed about the tool's behavior beyond the basic action.

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 sentence, which is concise and easy to parse. Every word earns its place. However, it is so brief that it sacrifices informative content, pushing the boundary of under-specification rather than conciseness.

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 (one nested object parameter, no output schema) and the ecosystem of sibling tools, the description is incomplete. It does not explain what a 'package' is in eBay context, how it relates to orders or shipping, or what data the 'packageRequest' expects. The agent lacks essential information to use the tool 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?

The input schema has 100% coverage (one parameter described), but the description of 'packageRequest' is minimal: 'Package creation data'. The tool description adds 'for international shipping' which gives context but does not explain the structure or required fields of the nested object. Baseline 3 is appropriate as the schema covers the parameter but the description adds limited value.

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 states 'Create a package for international shipping', which is a specific verb and resource. It clearly indicates the tool's purpose of creating a package, and the mention of 'international shipping' provides a scope. However, it does not differentiate from sibling tools like 'ebay_create_shipping_fulfillment' or other package-related tools, which slightly reduces clarity.

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 'ebay_create_shipping_fulfillment' or 'ebay_confirm_package'. There is no mention of prerequisites, conditions, or situations where this tool is preferred. The agent receives no help in decision-making.

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