decimal_to_dms

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It gives a single example but does not describe how negative values, rounding, or precision are handled, nor what the output structure is beyond the example. This is minimal transparency for a conversion tool.

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?

The description is extremely concise, using only three short lines to cover when to use, the parameter, and an example. There is no fluff or redundant information.

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 the presence of an output schema reduces the need to describe return values. However, the description lacks edge-case behavior (negative inputs, rounding, seconds precision) and provides only a single idealized example, making it just adequate rather than fully complete.

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?

The schema has zero description coverage, and the description compensates by stating the parameter `decimal` represents decimal degrees and provides a concrete example mapping decimal=10.5 to degrees=10, minutes=30, seconds=0. This adds meaningful context beyond the bare schema.

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 clearly states the conversion direction (decimal degrees to degrees/minutes/seconds components) using an arrow notation. It distinguishes itself from the sibling dms_to_decimal by naming the exact direction of conversion, though it lacks an explicit verb like 'convert'.

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?

The description begins with 'When:' and gives a clear condition for use, but it does not explicitly mention alternatives or tell when not to use this tool. It implies usage rather than providing direct guidance compared to sibling tools.

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