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

No annotations are provided, so the description carries the full burden. It mentions energy/conservation checks and includes a cost indicator ($0.01 USDC), which adds some behavioral context. However, it does not disclose side effects, resource usage, or whether the operation is read-only, leaving gaps.

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 two sentences, front-loaded with purpose and examples, and every phrase adds value. No redundancy or filler.

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?

While the input format is fairly well described (operation and spec with subfields), the description lacks details about the output format. Given no output schema, the user is left to infer what solving returns (e.g., solution array, energy values). The reliance on 'quantum_artificer_info' for spec shapes also creates incompleteness.

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?

The schema has 100% coverage but uses a generic description for 'spec' that defers to another tool. The description compensates by listing the expected fields (template, params, tSpan) and giving concrete examples of templates, adding significant meaning 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?

The description clearly states it solves coupled ODE systems and lists specific templates (orbital 2-body, oscillator, etc.). It distinguishes from siblings like 'chemistry' or 'quantum' by domain and approach, though it could explicitly contrast with 'numerical' for better differentiation.

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?

It provides usage instructions (operation='solve', spec with template, params, tSpan) and hints at use cases via example templates. However, it does not explicitly state when not to use this tool or offer alternatives among siblings, relying on implied context.

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