ebay_get_inventory_locations

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

No annotations are provided, so the description carries the burden. It does not disclose that the tool returns a paginated list, any auth requirements, rate limits, or side effects. The description 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 only four words, which is concise but borderline under-specification. It lacks any structural context or important details. It is front-loaded but does not earn its place by adding value.

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 lack of annotations, output schema, and the complexity of pagination, the description is incomplete. It fails to mention that the result is a list, that it is paginated, or what the response contains. A more complete description would note the pagination and scope.

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 already covers both parameters with clear descriptions ('Number of locations to return', 'Number of locations to skip'), so schema coverage is 100%. The description does not add any additional meaning or constraints beyond what's in the schema.

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 all inventory locations' clearly indicates it retrieves inventory locations, but it is vague about scope and pagination. The tool's parameters (limit, offset) suggest it returns a paginated list, but the description says 'all', which is misleading. It distinguishes from sibling ebay_get_inventory_location (singular) only by implication.

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 like ebay_get_inventory_location. There is no mention of prerequisites, context, or when not to use it.

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