chewy_inventory

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

With no annotations, the description carries full burden. It discloses that quantities are live and move between calls, that unresolved part numbers go to not_found, and that a 404 is returned if none resolve. It also lists the fields returned, which is essential behavioral information.

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 somewhat lengthy but every sentence adds value: purpose, unique value, live nature, error handling. It is front-loaded with the core purpose and structured logically, though it could be slightly tightened without losing information.

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 and no annotations, the description is exceptionally complete. It covers input format, batch size, output fields, uniqueness, live data caveat, and error handling (not_found and 404). An agent has everything needed to invoke it correctly.

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 description for part_numbers already covers the comma-separated format and up-to-20 limit (100% coverage). The description adds little beyond reinforcing that it's a batch call; it does not introduce new parameter semantics not already 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 clearly states the verb (look up) and resource (live warehouse inventory) and enumerates exactly what is returned (availability status, units on hand, inbound, reserved, available). It distinguishes itself from siblings by explicitly claiming it is the only Chewy surface with real quantities.

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?

It explicitly tells the agent when to use this tool over others: 'This is the only Chewy surface that carries real quantities' and contrasts with other endpoints that report booleans. It also specifies the batch limit of 20 and mentions the 404 behavior, giving clear selection criteria.

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