vtex_list_warehouses

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

No annotations are provided, so the description carries full burden. 'List all warehouses' implies a read-only operation returning multiple items, but it lacks critical behavioral details: pagination, sorting, filtering capabilities, rate limits, authentication requirements, or error conditions. For a list operation with zero annotation coverage, this is insufficient.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action ('List all warehouses') and contains no unnecessary elaboration. Every word earns its place, making it maximally concise while still conveying the basic purpose.

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's simplicity (0 parameters) but lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like pagination, return format, or error handling. For a list operation that might return large datasets, more context is needed to guide the agent effectively.

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 has 0 parameters with 100% description coverage, so the schema fully documents the absence of parameters. The description doesn't need to add parameter semantics, but it correctly implies no filtering parameters (just 'all warehouses'). Baseline for 0 parameters is 4, as the description aligns with the schema's emptiness.

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 'List all warehouses' clearly states the verb ('List') and resource ('warehouses'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'vtex_get_warehouse' (singular retrieval) or 'vtex_create_warehouse' (creation), which would require explicit comparison for a perfect score.

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 no guidance on when to use this tool versus alternatives. With siblings like 'vtex_get_warehouse' (retrieve specific warehouse) and 'vtex_create_warehouse' (create new warehouse), the agent must infer usage from the name alone. No explicit when/when-not or alternative recommendations are provided.

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