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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered structurally. The description adds the inputs and the return values ('Returns EOQ and orders/year'), but return values are already covered by the output schema, so the added behavioral value is modest. No edge cases (zero costs, unit mismatch, division-by-zero) are disclosed.

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?

Front-loaded with the purpose, then inputs, then outputs — a sensible ordering with no filler. The trailing 'See list_bundles...' sentence is mildly tangential but short and potentially useful for discovery, so it does not seriously hurt the structure.

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?

For a three-parameter, fully documented, read-only calculator with an output schema and rich annotations, the description supplies everything needed to invoke it correctly. The only genuine gap is the absence of units or guidance on invalid/zero inputs, which is minor given the schema minimums.

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%, so the baseline is 3. The description restates the three parameters ('annual demand, order cost, holding cost per unit') in essentially the same terms as the schema, adding no units, sign constraints, or interpretation beyond what is already documented.

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?

States a specific verb and resource ('Compute Economic Order Quantity') and even names the underlying method (Wilson formula), which unambiguously identifies the calculation among hundreds of calculate_* siblings. An agent can distinguish this from calculate_inventory_turnover without opening the schema.

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?

'Use for supply chain optimization' implies a domain but gives no concrete when-to-use or when-not guidance relative to adjacent finance/inventory calculators. The pointer to list_bundles is a discovery aid rather than a true alternative-tool routing rule.

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