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 mentions 'Get' which implies a read operation, but doesn't disclose any behavioral traits like whether it's idempotent, what errors might occur, performance characteristics, or output format. For a tool with no annotation coverage, this minimal description provides inadequate behavioral context.

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 at just 5 words with no wasted language. It's front-loaded with the core purpose. However, the extreme brevity comes at the cost of clarity and completeness, making it somewhat under-specified rather than optimally concise.

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 has an output schema (which handles return values) and 100% schema description coverage for its single parameter, the description's minimalism is partially excused. However, for a mathematical/symbolic computation tool with no annotations and many similar siblings, the description should provide more context about what 'head function' means and when to use it versus alternatives.

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 one parameter 'expr' documented as 'Expression'. The description adds no additional parameter semantics beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't need to given complete schema documentation.

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 head function of expression' states the action ('Get') and resource ('head function of expression'), but it's vague about what 'head function' means in the SymPy context. It doesn't distinguish this tool from its many siblings (e.g., sympy_args, sympy_atoms, sympy_free_symbols) that also analyze expression structure. The purpose is identifiable but lacks specificity.

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 over 100 sibling tools for SymPy operations, the description offers no context about typical use cases, prerequisites, or comparisons to similar tools like sympy_args. This leaves the agent guessing about appropriate application.

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