mcp-sympy

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

No annotations are provided, so the description carries full burden. It only states the action without disclosing behavioral traits like whether it's read-only, what format the output takes, error conditions, or computational complexity. For a tool with no annotation coverage, this is inadequate.

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 extremely concise with a single sentence, 'Get arguments of expression.', which is front-loaded and wastes no words. However, this conciseness comes at the cost of clarity and completeness.

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 no annotations, an output schema exists (which helps), but the description is too sparse. It doesn't explain what 'arguments' means, the tool's purpose relative to siblings, or behavioral aspects. For a tool in a complex mathematical context with many alternatives, this is insufficient.

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 description coverage is 100%, with the single parameter 'expr' documented as 'Expression'. The description adds no additional meaning beyond this, such as examples of valid expressions or constraints. Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Get arguments of expression' restates the tool name 'sympy_args' in slightly different words, making it tautological. It doesn't specify what 'arguments' means in this context (mathematical arguments vs. function parameters) or what type of expression it works with, failing to distinguish it from sibling tools like sympy_atoms or sympy_free_symbols.

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. With many sibling tools for expression analysis (e.g., sympy_atoms, sympy_free_symbols, sympy_coeff), the description offers no context about specific use cases, prerequisites, or comparisons.

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