ebay_get_listing_fees

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

No annotations are provided, so the description must fully convey behavioral traits. It states 'Get' implying a read-only operation, but it does not disclose any side effects, permission requirements, rate limits, or response format. The description is too brief to provide sufficient transparency.

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, clear sentence that conveys the core purpose without unnecessary words. It is front-loaded and earns its place, though slightly more detail could be included without harming 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 nested parameter structure and absence of output schema or annotations, the description is insufficient. It does not explain how to interpret the response, any prerequisites, or constraints (e.g., maximum number of offers). The tool is simple but the description lacks completeness.

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% description coverage with the 'offers' field described as 'Offers to calculate listing fees for'. The tool description adds no additional meaning beyond what the schema already provides, so the baseline score 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 tool retrieves listing fees for offers prior to publication, using the specific verb 'Get' and resource 'listing fees'. This distinguishes it from other eBay tools like ebay_get_offers or ebay_publish_offer.

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 mentions 'before publishing' to indicate when the tool is appropriate, but it does not specify when not to use it or suggest alternatives among the many sibling tools. Implied usage is clear, but explicit guidance is lacking.

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