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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false. The description adds value beyond those annotations by disclosing the deterministic formula and the return values (turnover and days-on-hand), which helps an agent understand the computation and output behavior.

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 front-loaded with the core formula and then quickly covers use case, inputs, outputs, and a related pointer. It is efficient, though the input listing is somewhat redundant given the schema.

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 an output schema present, the description need not explain return values, yet it does so concisely. Annotations cover the safety profile, and the description supplies the formula and use case. It could mention edge cases like the avg_inventory minimum, but the schema already enforces that.

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 100%, and the schema already documents both parameters with types, minimums, and descriptions. The description merely repeats 'Inputs: COGS, average inventory value' without adding syntax, format, or meaning beyond the schema, so the baseline 3 is appropriate.

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 states a specific verb and resource with an explicit formula (inventory turnover ratio = COGS / avg inventory), making the tool's function clear. It does not explicitly differentiate itself from sibling calculators such as calculate_inventory_eoq or other finance tools, so it falls short of a 5.

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 phrase 'Use for retail efficiency analysis' gives an implied use case, but there is no guidance on when not to use it or which alternative to choose. The pointer to list_bundles is a weak substitute for explicit alternatives.

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