ebay_get_package

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Get package details' which implies a read-only operation, but does not mention potential errors (e.g., if package not found), rate limits, or required permissions. This leaves significant gaps for the agent.

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 concise at one sentence. It front-loads the action and resource. However, it could benefit from additional context without being verbose, such as clarifying the type of package or linking to related tools.

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?

For a simple retrieval tool with one parameter and no output schema, the description is minimally complete but lacks essential context. It does not specify what a 'package' refers to (shipping, order, etc.), the return format, or how to use the ID. The presence of a similar sibling tool exacerbates the incompleteness.

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 schema coverage is 100% with a single parameter 'packageId' described as 'The package ID'. The description adds 'by ID' which is redundant. It does not explain the format or origin of the ID, but since coverage is complete, a baseline of 3 is appropriate.

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 the verb 'Get' and the resource 'package details by ID', making the purpose understandable. However, it does not distinguish itself from the sibling tool 'ebay_get_package_by_order_line_item', which also retrieves package details but by a different identifier.

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 is provided on when to use this tool versus alternatives such as 'ebay_get_package_by_order_line_item' or when not to use it. The description lacks context about prerequisites or scenarios.

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