dms_to_decimal

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

With no annotations, the description carries the burden and provides a concrete conversion formula, optional parameter defaults, and a worked example. It does not discuss edge cases, but for a simple pure function with an output schema these details are less critical.

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 brief and front-loaded, with a 'When:' opener followed by parameters and an example. Every sentence earns its place, and there is no filler.

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 deterministic conversion tool, the description, input schema, and output-schema signal cover the essential inputs, defaults, and expected behavior. Nothing important is missing at this complexity level.

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 0%, and the description fully compensates by identifying degrees as the core value, marking minutes/seconds as optional with defaults, and demonstrating the conversion via a clear example. This adds meaning 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 tool's purpose with 'sexagesimal ° ′ ″ → decimal degrees', a specific verb+resource pairing. The sibling decimal_to_dms makes the opposite direction obvious, so this tool is well differentiated.

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 leading 'When:' explicitly frames the condition for use: converting from sexagesimal to decimal degrees. It does not explicitly mention when not to use it or directly compare with decimal_to_dms, but the usage context is clear.

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