Warehouse

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing about cache behavior tied to the 'fresh' parameter or what the read returns, so it contributes no behavioral context beyond the 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 two words and therefore not verbose, but this is under-specification rather than effective conciseness. It fails to front-load any useful information about retrieval or the single warehouse concept.

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 details tool with no output schema and two parameters, the description should indicate what warehouse details are returned or how the result is shaped. Instead, it only says 'One warehouse,' leaving an agent without enough context to understand the response.

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%, with both warehouseId and fresh documented in the schema, so the baseline is 3. The description does not add meaning to either parameter, but the schema already carries that burden adequately.

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 'One warehouse.' is essentially a tautology that restates the title and singular form of the tool name. It does not state a specific verb or resource action such as retrieving warehouse details, and it provides no differentiation from siblings like warehouses or warehouse_documents.

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?

There is no guidance on when to use this tool, when to prefer the sibling 'warehouses' list tool, or what context is needed. The two-word description leaves all usage decisions to inference.

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