integrate

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

With no annotations, the description carries the full behavioral burden. It discloses one meaningful trait – the result is an indefinite integral (no bounds, no constant term implied) – but says nothing about behavior for non-integrable expressions, error reporting, or supported syntax, and there is no safety/mutation context at all.

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?

A single front-loaded sentence with zero filler; the operation and its scope are stated immediately.

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?

An output schema exists, so return values need not be explained, and the single sentence covers the core operation. However, for a symbolic-computation tool with two undocumented parameters, the absence of any input-format or failure-mode guidance leaves gaps an agent would want filled.

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. It does clarify that `variable` is the variable of integration (with `expression` as the integrand), but adds no syntax, format, or naming conventions for the expression string beyond what the parameter titles already imply.

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 (integrate) and resource (expression w.r.t. a variable) and the qualifier "indefinite" usefully separates it from a definite-integral tool. It is not explicitly differentiated from the sibling differentiate, but the operation is unambiguous from the name and sentence.

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 description gives no when-to-use guidance, no prerequisites, and never names an alternative such as differentiate or evaluate. Usage is only inferable from the tool name and the word "integral."

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