rr_get_demand_forecast

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

With no annotations provided, the description carries the full burden. It states the tool returns 'active forecast windows' but does not disclose whether it is read-only, the data freshness, or any side effects. Behavioral traits like permissions or performance are not addressed.

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 extremely concise, consisting of two clear sentences. It is front-loaded with the core purpose and avoids any unnecessary words or repetition.

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?

Despite moderate complexity (4 optional parameters, no output schema), the description does not explain what 'active forecast windows' means in terms of structure, how parameters combine (e.g., exclusivity of sku vs item_id), or if results are paginated. The description feels incomplete for effective use.

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%, so all four parameters have descriptions in the schema. The tool description adds no additional meaning beyond what the schema provides (e.g., 'Filter by store ID' is already in schema). The description mentions 'active forecast windows' but does not clarify parameter interactions.

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 retrieves demand forecast statistics (mu/sigma) for a SKU or item and returns active forecast windows. It uses a specific verb ('Get') and resource ('demand forecast'), and distinguishes itself from sibling tools like rr_create_location or rr_delete_agent_context by focusing on forecast retrieval.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of preconditions (e.g., at least one identifier required) or exclusions. The description lacks context for optimal usage.

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