get_stock_levels_updated_since

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

With no annotations provided, the description carries the transparency burden. It hints at performance (won't time out) but lacks details on side effects, rate limits, or data freshness. Output schema exists, so return format disclosure is not required, but additional behavioral traits would improve transparency.

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 with no redundant words. Front-loaded with the core action, then immediately adds practical advice. Every sentence adds value.

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 the tool's simplicity (one optional parameter, output schema present), the description is nearly complete. It covers purpose, parameter, and a key usage context. Minor omission: no mention of pagination or limits, but not critical for this scope.

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 only parameter 'days' is explained with its purpose ('last N days') and default value (7). Schema description coverage is 0%, so the description fully compensates by adding meaning beyond the JSON schema type.

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 returns 'Stock levels for products changed in the last N days' with a default of 7 days. It distinguishes from a potentially problematic sibling ('full StockLevels') by naming it and noting timeout issues.

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?

Directly advises to prefer this tool over 'full StockLevels' due to timeout risk, providing explicit alternative guidance. Does not cover other siblings (e.g., get_stock_levels_by_warehouse), but the context is sufficiently scoped.

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