dls_convert

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that conversion is bidirectional, omitting coordinate datum, DLS string format, supported provinces, validation behavior, or error handling. The description is not misleading, but it is far too minimal for a geo-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 two short sentences with no filler, front-loading the primary action and scope. The second sentence adds directional capability without repeating the first. It is an appropriately sized definition, even though it lacks operational detail.

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?

This is a two-way converter with conditional inputs, province qualifiers, and five parameters, yet the description does not explain how to construct a valid call. Critical information such as required parameters per direction and supported DLS formats is missing. The presence of an output schema does not fill these invocation gaps.

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 does not explain how direction maps to lat/lon versus dls_string, nor does it clarify the role of province. The phrase 'GPS→DLS and DLS→GPS' implies the two modes, but the exact required parameters and accepted direction values remain undocumented. With five parameters, this is a significant gap.

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 converts between GPS coordinates and the DLS grid system and names both supported directions. The Western Canada scope adds useful precision. However, it does not explicitly distinguish itself from the sibling dls_batch tool, so it stops just short of full differentiation.

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?

No guidance is given on when to use this tool versus dls_batch or reverse_geocode, and no exclusions are mentioned. The direction support is helpful but does not tell the agent how to choose between modes or which inputs are needed for each direction. This is a capability statement, not usage guidance.

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