integrate

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

With no annotations, the description carries the burden and does so well: it discloses the success envelope {'result': ...}, the error envelope {'error': ...}, and the important semantic caveat that the constant of integration is omitted. It stops short of stating anything about expression-size limits or simplification guarantees beyond 'may be returned in simplified form'.

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?

Front-loaded one-line purpose followed by well-labeled Args/Returns/Examples/Notes sections. The five examples are slightly more than strictly needed, but for a 0%-coverage schema they substitute for parameter documentation and each demonstrates a distinct function class.

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?

No output schema and no annotations exist, so the description must supply everything, and it covers both return shapes, error behavior, the missing-constant caveat, and result simplification. An agent has everything needed to call this correctly and interpret the response.

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 0%, so the description must compensate fully, and it does: the expression argument's expected string syntax is demonstrated with four concrete inputs, and the variable parameter is documented with its default ('x') and the fact that other variables may be substituted, illustrated by integrate("x*y", "y").

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 and resource: 'Computes the indefinite integral of a mathematical expression with respect to a variable.' The scope word 'indefinite' plus the explicit variable-as-respect-to distinguishes it cleanly from siblings like differentiate and summation, and SymPy support is enumerated.

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?

Usage is only implied through the worked examples; there is no statement of when to choose integrate over differentiate, calculate, or summation, and no exclusions (e.g. no definite integrals with bounds). Adequate for a self-evident math operation, but no explicit routing guidance.

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