dls_batch

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the dual conversion direction and the 'Up to 100 items per batch' limit. But it does not explain behavior for invalid items, mixed input, province handling, or failure modes, leaving important behavior undocumented.

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 a single focused sentence followed by the key batch constraint. Every clause earns its place, and the most important scoping information is front-loaded.

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?

Although an output schema exists and return-value documentation is not needed, the input side is under-specified for a 3-parameter tool. An agent cannot reliably know what string to pass for 'direction' or what each item object should contain. The 100-item limit and batch intent help, but the missing semantic details leave the description incomplete.

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%, so the description must compensate. It offers a general sense that 'items' hold coordinates or DLS strings and that direction selects the conversion mode, but it never defines accepted direction values, the item object shape, or the role of 'province'. The description only partially compensates for the missing parameter documentation.

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 names a specific verb ('Convert'), a clear resource (GPS coordinates / DLS strings), and a well-defined scope: multiple conversions in a single batch. It implicitly differentiates from the sibling dls_convert by emphasizing batch and up-to-100-items behavior.

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 implies the tool is for batch conversions rather than single conversions, and it states the 100-item batch ceiling. However, it does not explicitly say when to prefer this over dls_convert or other sibling tools, nor does it mention any exclusions or fallback conditions.

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