Calculate the cosine of a number in radians. Use for trigonometric calculations in math, physics, and engineering, or chain steps via batch_calc for multiple dependent operations in one call.
Calculates the cosine of a number in radians. For several operations or chained steps in one call, use batch_calc.
| Name | Required | Description | Default |
|---|---|---|---|
| number | Yes | The number in radians to find the cosine of |
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 behavioral burden. It confirms the operation and unit, but does not disclose edge-case behavior (e.g., NaN, infinity, precision) or error handling, which is minimally adequate for a standard trig function but not rich.
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 sentences, front-loaded with the core operation and followed by a routing note for the sibling tool. Every sentence earns its place with no redundancy.
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?
Given the low complexity, complete schema coverage for the single parameter, and the absence of an output schema, the description is complete enough. It covers the operation, unit, and the relevant alternative for batch operations.
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%, and the parameter schema already documents that the number is in radians. The description repeats the unit but adds no additional syntax, range, or format guidance beyond what the schema provides, so the baseline of 3 applies.
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 states a specific mathematical operation (cosine) and the required input unit (radians). It clearly identifies the resource as cosine, distinguishing it from sibling trig functions by name and purpose.
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 explicitly tells the agent to use batch_calc for several operations or chained steps in one call, giving a clear alternative-selection condition. For a single cosine calculation, the purpose already implies this is the correct tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.