sympy_expr_type

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

No annotations exist, so the description must disclose behavioral traits. It only says 'Get type of expression,' without specifying what constitutes a 'type,' whether the operation is read-only, or any side effects. The lack of detail leaves the agent uncertain about the tool's behavior.

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 concise sentence, which is efficient for a straightforward tool. However, it could include a bit more structure (e.g., what the return value represents) without becoming verbose. Still, it earns points for brevity.

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?

With an output schema existing (acknowledged in context signals), the description need not detail return format. However, the lack of clarification on 'type' — whether it returns a SymPy type string or class name — makes the tool's output somewhat ambiguous. Adequate but not fully complete.

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?

The input schema covers 100% of the parameters, and the description adds no additional meaning beyond the schema's 'Expression' label. Baseline 3 is appropriate since the schema handles parameter documentation, but no extra value is added.

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 clearly states the action 'Get type of expression' with a specific verb and resource. It is a simple and clear purpose. However, it does not differentiate from sibling tools like sympy_args or sympy_repr_expr, which also return properties of expressions. A 4 reflects good clarity without distinction.

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 vs alternatives. The description provides no context about the appropriate scenarios, such as when to query the type versus other expression analysis tools. This leaves the agent without usage direction.

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