Server Quality Checklist

Tool Scores

• sympyA
  4.9/5.0
  Behavior5/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly describes safety boundaries (blocked system calls, file I/O, network access), execution constraints (must print() results), and error conditions with retry strategies, offering rich behavioral context beyond basic functionality.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is well-structured with clear sections (safety boundaries, input rules, workflow, retry guidance) and uses bullet points for readability. It is appropriately sized for the tool's complexity, though some sentences could be slightly more concise (e.g., the workflow steps are detailed but not overly verbose).

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's complexity (sandboxed code execution), lack of annotations, and low schema coverage, the description is highly complete. It covers purpose, usage, safety, parameters, workflow, and error handling. The presence of an output schema means return values need not be explained, and the description addresses all other critical aspects thoroughly.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters5/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema has 0% description coverage for its single parameter 'code', but the description compensates fully by explaining that 'code' is a string containing Python/SymPy math code, detailing input rules (single argument, must print()), and providing workflow examples. It adds significant meaning beyond the bare schema.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool's purpose as executing Python/SymPy math code in a sandbox environment. It specifies the exact functionality (execute code), the domain (math/SymPy), and the context (sandbox with safety boundaries), making it highly specific and unambiguous.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines5/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides explicit guidance on when and how to use the tool, including a recommended workflow (steps 1-4), input rules (single code argument, use print()), and retry guidance for specific errors (E_AST_BLOCK, E_TIMEOUT, E_MEMORY). It comprehensively covers usage scenarios and error handling.

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