integrate_expression

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

No annotations are provided, so the description carries the burden of disclosing behavior. It does explain the indefinite/definite distinction, but does not describe the return format, handling of symbolic constants, or any side effects (e.g., session state). For a calculation tool, the behavioral implications are minimal, yet the description lacks detail beyond the core capability.

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, concise sentence that immediately conveys the core functionality. It is front-loaded with the verb and avoids unnecessary elaboration. Every word earns its place, making it highly efficient.

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's simplicity, a 4-parameter schema with full descriptions, and the presence of an output schema, the description is largely sufficient. It clearly states the key capability (indefinite or definite integration) and the schema covers parameter details. The only missing element is explicit differentiation from sibling tools, but the description still provides enough context for an agent to invoke it correctly.

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 100%, with each parameter (variable, expression, lower_bound, upper_bound) already well-defined. The description adds no additional semantics beyond stating that integration can be indefinite or definite, which is already implied by the parameter defaults and descriptions. The schema carries the parameter meaning, so a baseline score of 3 is appropriate.

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 the specific verb 'Integrate' and clearly names the resource 'expression', while distinguishing between indefinite and definite integrals. The name and description together leave no ambiguity about the tool's function, differentiating it from siblings like differentiate_expression or limit_expression.

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 implies usage by noting the tool handles 'indefinite or definite with bounds', which tells the agent that bounds are optional. However, it does not explicitly mention alternatives or when not to use this tool compared to other calculus operations (e.g., differentiate_expression). No exclusions or alternative references are provided.

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