ebay_get_inventory_location

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

With no annotations provided, the description offers minimal behavioral insight. It states the tool performs a 'get' (read) operation but does not disclose response format, error conditions, or idempotence guarantees, leaving the agent uninformed.

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 at 4 words, with no unnecessary text. However, it could be slightly expanded to include important context without sacrificing 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 simple schema and no output schema, the description is incomplete. It fails to explain what the response contains or how to obtain the merchantLocationKey, leaving gaps for an agent to effectively invoke the tool.

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 schema covers the single parameter merchantLocationKey with description 'The merchant location key', so the description adds no additional meaning beyond the schema. The baseline score of 3 is appropriate as the description does not enhance parameter understanding.

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 a specific inventory location' clearly states the action (get) and resource (inventory location), distinguishing it from the plural sibling ebay_get_inventory_locations (which retrieves all locations) and other mutation tools like ebay_create_or_replace_inventory_location.

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. For instance, it does not mention that ebay_get_inventory_locations should be used to retrieve all locations, or provide context about prerequisites like needing a valid merchantLocationKey.

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