grocy_stock_volatile

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the endpoint and the categories of volatile stock returned, but says nothing about response shape, ordering, or whether missing products include zero-stock items.

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?

Three compact fragments with the result categories front-loaded. The raw endpoint path is arguably filler for an agent, but nothing is bloated or buried.

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?

With no output schema and no parameter documentation in either schema or description, the agent cannot know what due_soon_days controls or what the response entries contain. The description should explain the parameter's threshold semantics and at least sketch the returned fields.

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 description coverage is 0%, so the description must carry the burden for the single parameter. 'Optional due_soon_days' gives no units, default threshold, or effect (e.g., items expiring within N days); only the parameter name hints at meaning.

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 names the specific resource set ('due soon, overdue, expired, and missing products') and maps it to GET /api/stock/volatile, which is clearly distinct from product-level or overview siblings. It stops short of an explicit verb like 'list', but the purpose is 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?

There is no guidance on when to choose this over grocy_stock_overview or grocy_stock_product, nor any stated preconditions. The category names imply an expiry-monitoring use case, but the agent must infer that.

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