sympy_factorial

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

No behavioral traits beyond the input schema are described. The description adds no information about error handling, performance, or constraints that the annotations (which are absent) might otherwise provide.

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, consisting of a single word. While this saves space, it might be too brief to be maximally helpful. Still, it is not verbose or repetitive.

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 presence of an output schema, explanation of return values is not required, but the description lacks broader context about the tool's role, typical use cases, or relationship to other similar tools.

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?

With 100% schema description coverage, the input schema already documents the parameter's constraint. The description adds no additional meaning or context about how n is used or computed.

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 'Factorial.' is very brief and uses a noun phrase rather than a clear verb. It does not distinguish from sibling tools like sympy_binomial or sympy_gamma, which also compute combinatorial or related functions.

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. There is no mention of appropriate contexts, exclusions, or related tools despite many siblings.

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