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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds nothing beyond that, and 'Returns: {error}' is a templated placeholder that is actively unhelpful for a deterministic math solver with a defined output schema. No edge cases (no real roots, a=0, degree/c mismatch) are disclosed.

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?

Sentence one is well front-loaded and waste-free. Sentence two is boilerplate that does not earn its place: 'Returns: {error}' conveys nothing useful when an output schema exists, and the list_bundles cross-reference is marginal for a solver.

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?

With an output schema present, the description need not explain return values, so the only real obligations are disambiguation and edge-case framing. It omits differentiation from calculate_quadratic_equation and any handling notes, leaving it minimally adequate for a simple, low-risk math tool.

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 description coverage is 100%, so the schema already documents a, b, c, and the degree enum, making the baseline 3 appropriate. The description's equation forms loosely tie a/b/c to their roles, but adds no format, range, or constraint detail beyond the schema.

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?

States a specific verb (Solve) plus the resource and the two exact forms it handles (ax+b=0, ax²+bx+c=0), which is concrete enough for an agent to match inputs. However, it never distinguishes itself from the sibling calculate_quadratic_equation, which appears to cover the same degree-2 territory, so an agent cannot route between them from this text alone.

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 statement of when to use this versus the many other math calculators, and no note on the degree-2 vs degree-1 selection logic beyond restating the formulas. The pointer to 'list_bundles for related math calculators' is a browsing hint, not usage guidance or an alternative to this tool.

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