List warehouses

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

Annotations provide readOnlyHint=true, and the description adds value by disclosing pagination behavior and the status filter requirement/default. This goes beyond the schema's optional status field by clarifying the API's actual expectations. While it doesn't detail edge cases like auto-pagination limits, the provided context is useful and not contradictory.

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 two concise sentences, front-loaded with the core purpose and followed by a key behavioral note. Every word earns its place with no redundancy or filler.

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 tool has 4 parameters with full schema descriptions and a readOnlyHint annotation, the description covers the essential purpose and a critical API nuance. It doesn't repeat schema details, and while it could mention return structure or auto-pagination, the lack of an output schema makes this an acceptable level of completeness.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful context for the status parameter by clarifying that the API requires a filter but defaults to ACTIVE, which is not obvious from the schema alone. This nuance enhances understanding beyond the structured definitions.

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 tool's function with a specific verb ('List') and resource ('warehouses'), and adds 'paginated' to convey scope. This distinguishes it from sibling tools like get_warehouse (single retrieval), create_warehouse, update_warehouse, and warehouse_action.

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?

The description provides clear context for when to use this tool (to list warehouses) and notes the API's status filter requirement with a default. While it does not explicitly mention alternatives or exclusions, the sibling tool names make the distinction obvious, and the pagination hint implies use for listing multiple items.

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