forecast_demand

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

No annotations provided, so description carries full burden. It mentions using TimesFM 2.5 model and returning markdown table with confidence bands, but does not disclose if it is read-only, requires permissions, data freshness, or side effects. For a forecasting tool, behavioral traits like 'safe to call repeatedly' or 'requires historical data' are missing.

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?

Two sentences: first states overall purpose and output format, second clarifies a key parameter behavior. No wasted words, front-loaded with the core action.

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 having output schema (not shown), description only covers group_by, group_value, and confidence bands. Missing explanation for lead_time_days, safety_factor, store, top_n, horizon_days, and metric enumeration. For a tool with 8 parameters and multiple sibling tools, this is incomplete.

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 descriptions already cover all 8 parameters (group_by, group_value, metric, etc.) with defaults and ranges. Description adds value only for group_value='all' behavior. Baseline 3 due to high schema coverage.

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 verb and resource: 'Forecast demand by product, collection, or SKU'. It distinguishes from sibling forecast_revenue by mentioning multiple metrics (units, revenue, orders) and the use of TimesFM 2.5. The 'all' case for top N groups is also specified.

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?

Provides some usage context: when group_value='all', forecasts top N groups by historical volume. However, no explicit guidance on when to use this tool vs siblings like forecast_revenue or analyze_promotion. No 'when not to use' or prerequisites stated.

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