Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full disclosure burden. It conveys the acceptable input shapes and the two output formats, which is the meaningful behavior for a pure conversion function, but it says nothing about precision/rounding, invalid-input handling, or hemisphere/sign conflict failures.

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 tight sentence with the resource and both output modes front-loaded and no filler. It is essentially the title with slightly more detail, so it is efficient but not maximally informative per word.

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?

An output schema exists, so return-value documentation is not required, and the schema fully documents the inputs. For a low-complexity, three-parameter conversion tool the description is nearly sufficient, with only failure-mode context 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 description coverage is 100% and the schema itself enumerates the accepted latitude/longitude string forms in detail. The description only restates the decimal-vs-DMS choice already covered by the schema, so baseline 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?

States a specific verb pair (parse/format) and the exact resource (latitude and longitude), with the two output modes named. It is distinct from the calculate_* siblings, but the description never explicitly differentiates itself from convert_speed or the calculation tools, so it falls short of a 5.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives among the siblings. The agent must infer from the purpose alone that this is the tool for coordinate reformatting rather than distance/bearing math.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.