cvp_breakeven__breakeven_units

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

With no annotations and a terse description, there is no disclosure of behavioral traits such as whether the tool calculates break-even units, or any prerequisites, side effects, or limits.

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?

While extremely short, the description sacrifices all informative content for brevity, making it useless. It does not front-load critical 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 the lack of output schema, parameter descriptions, and the presence of many sibling tools, the description is entirely incomplete and fails to equip an agent for correct invocation.

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 schema has 0% description coverage, and the tool description adds no meaning to the three parameters ('price', 'fixed_costs', 'variable_cost'). The agent gains no insight beyond their names.

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 '[cvp-breakeven] breakeven_units' is a tautology that merely restates the tool name without explaining what it computes. It fails to specify the verb or resource, leaving the purpose ambiguous.

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?

No guidance is provided on when to use this tool over the many sibling CVP tools (e.g., breakeven_sales, contribution_margin). The description offers no context for selection.

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