ratio_calc

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

Explains the core logic (finding missing value) and parameter roles. Lacks disclosure on error handling or invalid inputs, but acceptable for a simple math tool given no annotations.

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?

Extremely concise: one sentence for purpose followed by a clear parameter list. No unnecessary words.

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?

Sufficient for a straightforward calculator with output schema. Missing details like rounding or result format, but covers the essential behavior.

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?

Adds meaningful descriptions for all four parameters beyond the schema (which has only titles). Clarifies that 'a' and 'b' are first ratio values, 'value' is the known value, and 'side' indicates which side it represents.

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?

Clearly states the tool solves ratio proportions (a:b = c:d). However, it does not differentiate from sibling 'proportion_calc' which likely has similar functionality.

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 on when to use this tool versus alternatives (e.g., proportion_calc). Does not mention prerequisites or edge cases.

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