get_stock_levels_by_warehouse

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

No annotations provided, so description carries full burden. It states it returns stock levels but does not disclose read-only nature, authentication needs, or pagination. With 0% schema coverage, more behavioral context is expected.

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?

Single sentence of 13 words, front-loaded with key information. No fluff, but could be slightly more structured (e.g., separating warehouse filter from recency filter).

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 an output schema exists, description doesn't need return details. However, it omits comparison to similar siblings and doesn't mention scope (e.g., all products or active only). Adequate but not thorough.

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 0%, so description must add meaning. It explains updated_since_days (recency filter with default) but does not add beyond the parameter names. warehouse_id gets no extra context. Partial compensation.

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?

Description clearly states it retrieves stock levels filtered by warehouse and recency of update. It distinguishes from siblings like get_stock_levels_updated_since (which likely lacks warehouse filter) and other get/list tools, making the purpose specific and unambiguous.

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 use when needing stock levels for a specific warehouse with optional recency filter, but lacks explicit guidance on when to use this tool versus alternatives (e.g., get_stock_levels_updated_since). No when-not or alternative tools mentioned.

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