integrate_expression

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core operation and does not disclose output behavior, supported input formats, limitations, or whether an integration constant is returned. 'Computes the indefinite integral' is essentially the operation itself, not an additional behavioral trait.

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 focused sentence that front-loads the operation and contains no redundant information. Every word contributes to understanding what the tool does.

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 two-parameter symbolic computation tool, this is minimally viable: it names both parameters and the operation. However, with no annotations, no schema descriptions, and no output-schema details, key operational aspects like input formatting and error behavior are left to inference.

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 0% parameter description coverage; the description does clarify that 'expression' is the integrand and 'variable' is the integration variable. However, it gives no details about accepted expression syntax, variable notation, or whether expressions must be in a particular format such as SymPy.

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 uses a specific verb ('Computes') and clearly names the resource ('the indefinite integral of an expression with respect to a variable'). This distinguishes it from sibling tools like differentiate, which compute derivatives, and solve_equation.

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?

The purpose implies when to use this tool—whenever an antiderivative is needed—but it provides no explicit guidance about alternatives or when not to use it. There is no mention of sibling tools or exclusions, leaving usage context mostly implicit.

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