Compute the angle in radians whose tangent equals a given number. For multiple or chained calculations, use batch_calc to run steps in one call.
Calculates the arctangent (in radians) of a number. For several operations or chained steps in one call, use batch_calc.
| Name | Required | Description | Default |
|---|---|---|---|
| number | Yes | The number to find the arctangent of |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries full burden. It discloses that the result is in radians, which is useful for interpretation. However, it doesn't mention potential domain restrictions (e.g., arctangent accepts all real numbers), precision, or return format beyond the unit.
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?
Two concise sentences, front-loaded with the core function and then the alternative. No waste.
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?
For a simple single-parameter math function with full schema coverage and no output schema, the description provides what is needed: the operation, unit, and routing to batch_calc. Nothing critical is missing.
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 coverage is 100%, so the parameter is fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides.
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?
States a specific verb (Calculates) and resource (arctangent), and specifies the unit (in radians), which distinguishes it from sibling trigonometric tools.
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?
Names the alternative (batch_calc) for several operations or chained steps, giving clear context. No explicit when-not-to-use beyond that, but sufficient for a single-purpose tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.