solve_inequality

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

Discloses the degree range (1–4) and shows a concrete example, but with no annotations, it doesn't describe output format, error handling, or side effects. The output schema covers return values, so some burden is relieved.

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?

Three-line structured description with 'When:', 'Params:', and 'Example:' sections. No wasted words, though it could be slightly more verbose for clarity.

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?

Covers the essential operational context: degree limitation, parameter semantics, and an example. It doesn't explain what the solution looks like, but the output schema exists; for a tool of this simplicity it's adequate.

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?

Schema has no property descriptions (0% coverage), so the description fully compensates: it defines coefficients as [a0,...,an], lists allowed relation values, and provides a worked example.

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 it solves polynomial inequalities of degree 1–4, with explicit parameter description and example. Distinguishes from sibling tools like solve_polynomial (equations) and solve_linear by its inequality focus and degree range.

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?

Provides a 'When:' clause specifying the tool's intended use (polynomial inequality solving). It does not explicitly list alternative tools or exclusions, but the degree constraint and inequality nature imply when not to use it.

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