solve_ode

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the generic purpose. It does not mention whether the solution is symbolic or numeric, how initial conditions are handled, what happens if no closed-form solution exists, or any side effects, leaving the tool's actual behavior opaque.

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 sentence, but it is under-specified and essentially restates the tool name 'solve_ode'. Rather than being concise, it fails to add meaningful information, making it inadequately sized for a tool with multiple parameters and potential ambiguity.

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?

Given the tool has an output schema and three parameters, the description should provide more context, such as what types of ODEs are supported or what output format to expect. Without annotations, the description is too sparse to fully support an agent in invoking the tool appropriately, especially with sibling tools like solve_equation nearby.

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?

All three parameters have descriptions in the input schema, so the schema already fully documents the parameters. The description adds no additional parameter context beyond what the schema provides, which is acceptable per the baseline.

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 the verb 'Solve' and the resource 'ordinary differential equation', identifying the tool's core function. However, it does not differentiate from sibling tools like solve_equation, which could also be interpreted as solving equations, so it lacks that distinguishing specificity.

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 alternatives such as solve_equation or integrate_expression. The description gives no context, prerequisites, or exclusions, leaving the agent without direction on tool selection.

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