sympy_symbolic_add

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

No annotations are present, and the description does not disclose behavioral traits such as side effects, computational limits, or return format. The tool likely performs a pure computation, but the description fails to confirm this.

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 very concise at two words plus a parenthetical qualifier. It is front-loaded with the key action. However, conciseness comes at the cost of valuable detail, making it less helpful.

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 (symbolic computation) and the availability of an output schema (not shown), the description is too sparse. It does not explain what the output represents, error conditions, or how the addition is performed (e.g., algebraic simplification).

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 coverage is 0%, so the description is the only source of parameter meaning. It adds 'comma-separated' to the 'terms' parameter, which provides some clarity beyond the schema's type string, but does not explain how terms should be structured (e.g., single symbols or expressions).

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 clearly states it performs symbolic addition, with the qualifier 'comma-separated,' which hints at the input format. It distinguishes from siblings like sympy_symbolic_mul by the verb 'addition,' though it could be more explicit about the type of symbolic expressions involved.

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_sum or sympy_symbolic_mul. The description only mentions comma-separated input, leaving the agent without context for appropriate usage.

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