list_inventory

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

The description says 'List all inventory items', but the schema includes skip and limit parameters, indicating pagination—meaning it does not list all items in one call. This contradiction misleads about the tool's behavior. No annotations are present to clarify safety or side effects.

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 three words, which is too sparse for a list tool with pagination. It lacks necessary details about ordering, filtering, or result format, making it underspecified.

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 absence of an output schema and the presence of pagination parameters, the description fails to explain what the tool returns or how to handle paginated results. It is incomplete for effective use.

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 provides full coverage with descriptions for both parameters (skip, limit). However, the description's claim of 'all' conflicts with the pagination behavior implied by the schema, adding confusion rather than clarifying parameter usage.

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 states the verb 'List' and the resource 'inventory items' clearly. However, it does not differentiate from sibling list tools (e.g., list_buyers, list_products) which list different resources.

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 is provided on when to use this tool versus alternatives like list_products or list_buyers. There are no exclusions or context for preferred use.

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