calculate_headingCalculate the azimuth between two Maidenhead grid locators to determine beam heading for amateur radio contacts.
Calculates heading (azimuth) between Maidenhead locators.
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | ||
| start | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the safe, read-only, idempotent, non-destructive behavior. The description adds domain context about azimuth and Maidenhead locators, but does not explain direction convention, units, or edge cases.
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?
A single front-loaded sentence with no filler; appropriately sized for a simple calculation tool.
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?
The tool is simple and annotations plus output schema cover much of the context. However, the description leaves meaningful gaps around parameter format and start-to-end direction semantics.
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 0%, so the description must compensate. It indicates both inputs are Maidenhead locators, but does not specify locator format or clarify that heading is computed from start to end.
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 verb and resource: calculates heading/azimuth between Maidenhead locators. It is clearly distinct from calculate_distance by output type, though it does not explicitly reference that sibling.
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 implies the tool is for heading calculation between locators, but gives no explicit when-to-use guidance, prerequisites, or comparison to calculate_distance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.