ebay_get_handover_sheet

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

No annotations are provided, so the description must disclose all behavioral traits. It only states a simple action without explaining what a handover sheet is, whether it returns a PDF, or any side effects (none expected). Minimal insight.

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 very concise (4 words), but is too brief to cover necessary details. While it is structurally simple, it sacrifices completeness for brevity.

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 no output schema and a large set of sibling tools, the description is insufficient. It does not explain the return format, how to specify which package, or how it differs from related tools like 'ebay_get_package' or 'ebay_get_labels'.

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 100%, and the description adds an example ('bundle_id') for the 'params' object. However, the schema already describes 'Query parameters (e.g., bundle_id)', so the description adds little additional meaning beyond what is already structured.

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 'Get handover sheet for packages' uses a specific verb and resource, clearly indicating the tool retrieves a handover sheet. It is distinct from sibling tools like 'ebay_get_bundle_label' or 'ebay_get_labels' by name, though no explicit differentiation is provided.

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 versus alternatives. The description does not specify context such as prerequisites (e.g., needing a specific ID) or when not to use it.

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