sympy_args

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 'Get arguments of expression' without revealing expected output format, error cases (e.g., expression with no arguments), or whether it works on all expression types. This is insufficient for safe invocation.

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?

A single, efficient sentence with no redundant words. However, it could be more informative while remaining concise. The structure is minimal but not wasteful.

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?

Despite having an output schema (not shown), the description is too sparse. For a symbolic math tool, it should clarify what 'arguments' means (e.g., function arguments, operands). The description adds no actionable context beyond the schema.

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?

Input schema has 100% description coverage for the 'expr' parameter ('Expression'). The description adds no new semantics beyond restating 'arguments of expression'. Baseline 3 is appropriate given high schema coverage.

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' clearly states the verb (get) and resource (arguments of an expression), distinguishing it from siblings like sympy_arg which likely retrieves a single argument. However, 'arguments' is slightly ambiguous in SymPy context—could be method arguments or function arguments.

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 on when to use this tool versus alternatives like sympy_arg, sympy_atoms, or other expression manipulation tools. The description does not mention prerequisites or context for invoking this tool.

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