sim_break_even

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only states the outcome (solving for an input value) but does not disclose whether the tool is read-only, what happens if no solution exists, whether it requires a web service call, or any side effects. The lack of detail is a significant gap.

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 very concise—a single sentence that front-loads with 'SIMULATE' to set context. However, it is too brief to provide meaningful structure or guidance for a tool with 8 parameters, and the lack of segmentation makes it less useful than a slightly longer, organized description.

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 moderate complexity (8 parameters, nested objects, no output schema), this description is grossly incomplete. It gives no information about input semantics, expected output, error handling, or relationship to other simulation tools, making it impossible for an agent to reliably select and invoke the tool correctly.

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 input schema has 8 parameters with 0% schema description coverage, and the description itself provides no explanation of any parameter. It does not clarify what 'template', 'solve_for', 'target_value', or other fields mean or how they relate to the break-even goal, leaving an agent with no semantic grounding.

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 clearly states the tool's purpose: solving for an input value that causes a metric to hit a target. This distinguishes it from sibling tools like sim_sensitivity (which analyzes sensitivity) and sim_run (which runs simulations) by specifying the break-even objective.

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 on when to use this tool versus alternatives. The description does not mention any prerequisites, such as needing a template from sim_list_templates, or when it should be preferred over sim_sensitivity or sim_compare. No exclusions or alternative recommendations are provided.

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