sympy_apart

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

No annotations provided, yet the description only states the operation without any behavioral details such as whether it modifies state, requires specific permissions, or handles edge cases. It doesn't even hint that it returns a result.

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 short sentence with no extraneous words. It fronts the core action effectively.

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 (1 parameter, output schema exists) and the domain (symbolic math), the description minimally suffices. However, it does not mention the variable or format input, but the schema covers that. A slightly richer description would improve completeness.

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 input schema already provides 100% coverage for the single parameter 'expr' with description 'String rational expression'. The tool description adds no additional meaning beyond what the schema conveys.

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 'Perform partial fraction decomposition' clearly states the specific operation. Among many sibling tools, this uniquely identifies a well-known algebraic transformation, making its purpose unambiguous.

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?

No guidance on when to use this tool versus alternatives (e.g., sympy_simplify or sympy_factor). The description does not mention input prerequisites or scenarios where partial fraction decomposition is appropriate.

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