Get warehouse

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds the return fields (title, slug, status), which is useful context. It does not disclose error behaviors (e.g., 404 if not found) or any filters, but the annotation lowers the bar; this meets the minimum viable level.

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 concise sentence with front-loaded verb and resource. It includes essential context (return fields) without any waste.

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 simple single-parameter read operation with a readOnly annotation and no output schema, the description is sufficient. It mentions the return fields, which is enough for typical use. It doesn't explain error handling, but that's not critical for a basic getter.

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 already provides complete coverage of the only parameter ('Warehouse ID (UUID)'), so the description adds no extra semantic value. Baseline of 3 is appropriate because the schema does the heavy lifting.

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: 'Get a single warehouse by its ID' and lists the specific fields returned (title, slug, status). This distinguishes it from sibling tools like list_warehouses (which retrieves all warehouses) and update_warehouse/create_warehouse (which mutate).

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 implies the use case: when you have a warehouse ID and need a single warehouse's details. It contrasts with list_warehouses by specifying 'a single warehouse'. However, it does not explicitly mention alternatives or when not to use this tool, so it falls short of full explicit guidance.

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