Convert an angle from radians to degrees for trigonometry, geometry, and math calculations. Provide the radian value and get the equivalent degree measure.
Converts radians to degrees. For several operations or chained steps in one call, use batch_calc.
| Name | Required | Description | Default |
|---|---|---|---|
| number | Yes | The number in radians to convert to degrees |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. For a pure, side-effect-free math conversion there is little behavior to disclose, and the description adds the batch routing hint, but it says nothing about return format or handling of extreme/large values. Adequate but minimal.
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 short sentences, purpose front-loaded and the alternative routing second. Zero filler; every sentence earns its place.
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 single-parameter pure conversion with no output schema and no side effects, the description plus schema is essentially complete. Only a note on return representation would add anything, which is minor for such a trivial function.
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 a single documented parameter, so the schema already explains the input fully. The description adds no format, range, or unit nuance beyond what the schema states, which is the expected baseline.
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 and resource ('Converts radians to degrees'), which is unambiguous against the many arithmetic siblings. It does not explicitly contrast with the closest sibling, degreesToRadians, but the direction of conversion is inherent in the name and description.
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 and the condition that selects it ('several operations or chained steps in one call'). It lacks when-not guidance for the inverse operation, but the routing advice to the batch sibling is concrete and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.