sympy_factor

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

No annotations are provided, so the description bears full burden. It only states 'Factor an expression' without disclosing limitations (e.g., it may not factor all expressions, or it might handle symbolic vs numeric). This is insufficient for an agent to anticipate behavior.

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 extremely concise (3 words). It is front-loaded and contains no filler. However, it is so brief that it sacrifices clarity on purpose and usage.

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 complexity (1 param, no annotations), the description is too minimal. It does not explain what factoring entails, expected output, or behavior for invalid inputs. The output schema exists but is not referenced.

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 covers 100% of parameters with a description for 'expr'. The tool description adds no extra meaning beyond the schema. Baseline 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 'Factor an expression' uses a specific verb and resource, clearly indicating the tool's action. It is distinguishable from siblings like sympy_factorint (integer factorization) and sympy_simplify. However, it could be more specific about what types of expressions are factored (e.g., polynomials).

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 is provided on when to use this tool versus alternatives like sympy_factorint, sympy_simplify, or sympy_expand. The description does not mention prerequisites, exclusions, or context for factoring.

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