sympy_re

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

No annotations provided, so the description carries full burden. The minimal description does not disclose that it operates on sympy expressions, returns a sympy object, or has any constraints. The output schema exists but is not visible here.

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 at two words, but arguably under-specified. For a simple function, it may be acceptable, but given the large number of siblings and lack of other context, it borders on vague.

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?

With 0% parameter coverage, no annotations, and a one-line description, the tool is severely underspecified. The agent cannot infer input format or output nature, making it nearly unusable without external knowledge.

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 parameter 'expr' has no description in schema (0% coverage). The description 'Real part.' does not explain what type of expression is expected or acceptable values. Leaves the agent guessing.

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 'Real part.' clearly states the operation on a complex expression. It distinguishes from sibling tools like 'sympy_im' (imaginary part) and 'sympy_abs'.

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 like 'sympy_as_real_imag' or 'sympy_conjugate'. Lacks context for selection.

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