markup_calculator

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

With no annotations, the description carries full responsibility. It only states what the tool does without disclosing behavioral traits such as handling of edge cases, precision, negative values, or error conditions. This is a significant gap for a calculation tool.

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 a single, front-loaded sentence that captures the essence of the tool. There is no extraneous information, and it effectively communicates the tool's functionality.

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?

The description is sufficient for a simple calculator with well-documented parameters, but it does not mention the return value or format. Given the lack of output schema and annotations, slightly more detail about output behavior would improve completeness.

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 adds context by explaining the two calculation modes, which helps the agent understand how parameters relate. However, since the input schema already has 100% coverage with descriptions for each parameter, the added value is minimal but present.

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 two specific functions: calculating selling price from cost and markup percentage, or finding markup from cost and price. It is concise and distinguishes the tool from general calculators, though it does not explicitly differentiate from the sibling profit_margin_calculator.

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 versus similar siblings like profit_margin_calculator or discount_calculator. The description implies usage for markup-related calculations but lacks explicit context or alternatives.

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