calculate_inventory_turnover

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

No annotations provided. Description discloses return values (turnover and days-on-hand). While it doesn't mention read-only nature, it's implied as a calculation. No contradictions.

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 concise sentences: first states function and formula, second gives usage and reference to related tools. No extraneous information.

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 simple inputs (2 required params) and presence of output schema, description adequately covers purpose, formula, and outputs. References related tools for broader context.

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 covers both parameters with descriptions and constraints. Description restates parameter names but adds no new semantic detail beyond the schema. Baseline 3 as schema coverage is 100%.

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 the tool computes inventory turnover ratio with explicit formula (COGS / avg inventory) and domain (retail efficiency analysis). Includes reference to related calculators via list_bundles, distinguishing it from numerous sibling calculate-* tools.

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?

Explicitly states use case 'retail efficiency analysis' and directs to list_bundles for related 'finance-universal' calculators, implying alternatives. Could be more explicit about when not to use, but sufficient context.

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