List Warehouses

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by disclosing pagination behavior (1-based pages, page_size cap of 200), response_format options, and the return composition (UUID, code, name). No contradiction with annotations.

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 well-structured, starting with a clear purpose sentence, followed by an Args section and a Returns line. It is slightly redundant with the schema, but not bloated, and every section is easy to scan.

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 read-only list endpoint with rich schema and annotations, the description supplies pagination limits, output format options, and return purpose. It is sufficient for an agent to select and invoke the tool correctly without needing an output schema.

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 input schema covers 100% of parameters with detailed descriptions including defaults and ranges. The Args section in the description mostly repeats schema content, adding little new meaning beyond quick readability, so the high-coverage baseline of 3 is appropriate.

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 opens with a specific verb-resource pair: 'List the warehouses configured in the account, paginated.' It clearly identifies the scope and differentiates from sibling tools like logiwa_list_warehouse_locations and other list_* tools by naming the exact resource.

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 states the return value is 'used to resolve warehouseIdentifier / warehouse code for other tools', giving concrete context for when this tool is needed. It does not explicitly name alternatives or exclusions, but the purpose is specific enough to guide selection among siblings.

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