solve_quadratic

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

Minimal disclosure: only states it returns real or complex roots. No mention of degenerate cases (a=0), number of roots returned, or output format. Annotations are absent, so description carries full burden but fails to provide sufficient behavioral context.

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?

One sentence, 10 words, very concise. Front-loaded with purpose. However, missing important details reduces overall utility of conciseness.

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?

For a simple quadratic solver with no output schema or annotations, description is inadequate. Does not specify output format (e.g., array of roots), handling of discriminant, or edge cases. AI agent may invoke incorrectly without additional context.

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?

Description implicitly defines parameters as coefficients of the quadratic equation, adding meaning beyond schema names. However, it does not explain constraints (e.g., a should not be 0) or potential types beyond numbers. With 0% schema coverage, description partially compensates but is not comprehensive.

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 verb 'Solves' and the specific equation a*x^2 + b*x + c = 0, and mentions return type (real or complex roots). Distinguished from sibling tools as no other solves quadratic equations.

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. Does not mention edge cases or prerequisites like a != 0.

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