ebay_get_listing_fees

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

No annotations provided, so the description carries the full burden. While 'Get listing fees before publishing' suggests a read-only operation, it does not explicitly state that it is non-destructive, requires no authorization beyond normal, or what happens to data. It remains vague on behavioral traits.

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 of 8 words, concise and front-loaded with the key action and resource. No wasted words.

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?

Despite having a single parameter and no output schema, the description is insufficient. It does not clarify the return value (listing fees structure) or any constraints. The brief phrase 'before publishing' hints at use case but leaves gaps.

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% with a description for the 'offers' parameter, so baseline is 3. The tool description adds no additional meaning beyond what the schema provides. It does not explain how to structure offers or which fields are required.

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 'Get' and clearly identifies the resource 'listing fees' with context 'for offers before publishing'. It effectively distinguishes from sibling tools like ebay_create_offer 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 implies usage before publishing an offer but does not explicitly state when not to use it or mention alternatives. It lacks explicit guidance on prerequisites or comparison with related tools like ebay_get_offer.

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