sympy_as_numer_denom

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

With no annotations and a single-sentence description, behavioral traits (e.g., output structure, edge cases, error handling) are entirely absent. The description does not disclose any operational details.

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?

Extremely concise but under-specified. Not a model of efficiency; it sacrifices informativeness for brevity. Lacks any structure or front-loaded key facts.

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?

Despite having an output schema, the description does not clarify what the tool returns (e.g., a tuple of numerator/denominator). Incomplete for a SymPy algebraic manipulation tool with many siblings.

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 description adds no meaning to the parameter 'expr' beyond its type. Schema coverage is 0%, and the description fails to explain what input format or constraints apply.

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?

Description 'As numerator and denominator' is vague and barely clarifies the tool's action. It restates the name without specifying extraction, transformation, or usage context.

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 siblings like sympy_simplify, sympy_apart, or sympy_ratsimp. No usage context or alternatives mentioned.

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