ebay_get_listing_locations

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

No annotations provided, so description must stand alone. It discloses that this is a read operation (via 'Get') and specifies OAuth scopes, but lacks details about the response structure, pagination, or rate limiting. For a read tool, minimal behavioral context is given.

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, with two succinct sentences: one for purpose and one for OAuth scope. It front-loads the key information, though it could benefit from a slightly more structured format (e.g., bullet points for scopes).

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 tool with no output schema, the description should explain what data is returned (e.g., location IDs, names, coordinates). It does not, leaving the agent uncertain about the response. Given low complexity (2 params), more detail is expected.

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 no additional meaning beyond the schema's parameter descriptions. The mention of 'SKU location mapping' indirectly references the sku parameter, but does not enhance understanding. 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 it gets inventory locations for a specific listing via SKU location mapping. It is specific enough to distinguish from other 'get' tools like ebay_get_inventory_locations and ebay_get_inventory_location, but could be more explicit about what 'inventory locations' means (e.g., warehouse IDs or addresses).

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 such as ebay_get_inventory_locations or ebay_get_inventory_location. It only includes OAuth scope requirements, which are necessary but not sufficient for usage direction.

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