break_even_calculator

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

With no annotations, the description carries the full behavioral disclosure burden. It does not explain what happens when variableCostPerUnit is omitted, whether values are rounded up to whole units, what occurs if pricePerUnit <= variableCostPerUnit, or what the return format is. The formula and edge cases are entirely undisclosed.

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 concise and front-loaded with the core purpose, followed by a compact input list. It avoids unnecessary words, but the input list could have been used to add behavioral caveats rather than merely repeating schema properties.

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 tool with no annotations, no output schema, and four parameters with minimal schema documentation, the description is incomplete. It does not explain the calculation formula, defaults for optional parameters, return type, or constraints, leaving an agent to guess critical operational details.

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 description lists parameters and marks targetProfit as optional, but it also implies variableCostPerUnit is required by not marking it optional, contradicting the schema which lists only fixedCosts and pricePerUnit as required. It adds minimal meaning beyond the schema (which has 0% description coverage) and does not explain each parameter's role or default behavior.

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 exactly what the tool does: 'Calculate break-even point in units.' The verb 'calculate' and the specific resource 'break-even point in units' are unambiguous, and this clearly distinguishes it from the fee and margin calculators among its siblings.

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 about when to use this tool versus the sibling calculators. It only lists inputs, with no mention of scenarios (e.g., 'when you need to know how many units to sell to cover fixed costs'). No exclusions, prerequisites, or alternatives are named.

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