sympy_as_real_imag

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

With no annotations provided, the description must disclose behavior. It does not state the output format, whether the tool is read-only, or any side effects. This is a critical gap for a tool that likely returns a tuple or pair of expressions.

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?

While the description is short, it sacrifices informativeness for brevity. It is under-specified rather than concise, as it fails to convey essential information.

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 (one parameter, output schema exists), the description should at least clarify the purpose. It does not, making it completely inadequate for an agent to understand and invoke the tool correctly.

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 only parameter 'expr' has no description. With 0% schema description coverage, the description should explain what the input string should represent (e.g., a SymPy expression). It does not, leaving the parameter ambiguous.

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 'As real and imaginary parts' is a tautology that merely restates the tool name 'sympy_as_real_imag'. It does not provide a clear verb or resource, and fails to distinguish the tool from siblings like sympy_re or sympy_im.

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 such as sympy_re, sympy_im, or sympy_expand_complex. The description is entirely silent on context.

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