ebay_get_categories

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

With no annotations provided, the description fails to disclose behavioral traits. It does not state that this is a read-only operation, mention authentication requirements, or describe the nature of the response (e.g., a hierarchical tree). The description is minimal and adds no behavioral context beyond the tool's name.

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 9 words, but it sacrifices necessary detail. While it is front-loaded and to the point, it omits critical information about parameters and usage, making it minimally adequate.

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 has 4 parameters, no output schema, and no annotations, the description is incomplete. It does not explain what the category tree contains, how it is structured, or how to use the parameters effectively. The description is too sparse to guide correct invocation.

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 4 parameters with only 25% description coverage (only category_tree_id has a description). The tool description adds no additional meaning for parameters like client_id, client_secret, and marketplace. Since schema coverage is low, the description should compensate but does not, leaving the agent without guidance on how to properly populate these fields.

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 the eBay category tree for a given marketplace. It uses a specific verb-resource pair ('Get' + 'category tree') and is distinct from sibling tools like ebay_get_item, ebay_get_item_by_legacy_id, and ebay_search, which focus on items or searches.

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 lacks any guidance on when to use this tool versus alternatives, such as ebay_search. It does not mention prerequisites like needing a marketplace identifier or how to determine the category_tree_id. The agent is left to infer usage from the schema.

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