sympy_symbol

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the creation action but does not mention whether the symbol is added to any environment, what the return value is (though output schema exists), or any side effects. For a simple creation, more context (e.g., 'returns a new Symbol object') would improve transparency.

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 a single, front-loaded sentence with no filler. It is concise, though extremely brief. It could slightly expand without losing conciseness.

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, the description does not need to explain return values. However, considering the large number of sibling tools and the simplicity of this function, the description is adequate but lacks extra context (e.g., 'Use this to create a new free symbol for algebraic manipulation').

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?

Schema coverage is 100% (single parameter 'name' well-described as 'Symbol name'). The description adds no extra meaning beyond what the schema already provides. Baseline of 3 is appropriate.

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 'Create a single symbolic variable' uses a specific verb ('Create') and clearly identifies the resource ('single symbolic variable'). It distinguishes from sibling tools like 'sympy_symbols' (which likely creates multiple) and 'sympy_symbols_create' (possible alternative).

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 explicit guidance on when to use this tool versus alternatives. The description does not mention that for multiple symbols, other tools like 'sympy_symbols' or 'sympy_symbols_create' should be preferred. This omission forces the agent to infer usage context.

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