Convert angles between degrees, radians, gradians, and turns, and retrieve corresponding trigonometric values for calculations.
Convert angles between degrees, radians, gradians, and turns. Includes trig values.
| Name | Required | Description | Default |
|---|---|---|---|
| from | Yes | Unit of input: degrees, radians, gradians, or turns. | |
| value | Yes | Angle value to convert. |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only the vague note "Includes trig values," without explaining output shape, precision, or what trig values are returned.
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 with zero waste, and the core conversion purpose is front-loaded before the supplemental trig note.
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 two-parameter conversion tool, the description plus 100% schema coverage and annotations are sufficient to call it correctly. The only minor gap is the unexplained "Includes trig values" return note.
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%, with both parameters documented directly in the input schema. The description repeats the supported units but adds no meaning beyond the schema's parameter descriptions.
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 uses a specific verb and resource: convert angles, with the four supported units named. It clearly distinguishes this from sibling conversions such as convert_temperature or convert_length.
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?
It states the operation clearly enough to imply when to use it, but gives no explicit when-to-use guidance versus related tools, nor any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.