List Warehouses

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

Discloses the return format (warehouse IDs and names) and the read-only nature. With no annotations, it adds basic behavioral context but omits details like data freshness, authorization requirements, or whether results are paginated.

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?

Three short sentences, each serving a distinct purpose: purpose, output, and usage. No redundancy, no fluff. Ideal conciseness.

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 zero parameters and no output schema, the description adequately covers what the tool returns and how it relates to other tasks (stock updates). Minor omission: could clarify if all warehouses or only active ones are returned.

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 coverage is 100% with no properties; description adds 'No parameters required' which only reiterates the schema. No additional semantic value beyond confirming parameter absence.

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?

Uses specific verb 'Get the list of seller warehouses', clearly identifies resource and scope (FBS warehouses). Distinguishes from sibling tools like get_warehouse_stocks which returns stock data, not warehouse list.

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?

Explicitly states the tool requires no parameters and explains a primary use case (get IDs for update_stocks). However, lacks explicit conditions when not to use or mention of alternatives.

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