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

With no annotations, the description is the only behavioral source. It usefully discloses that the conversion is 'offline' and that it transforms lat/lon into MGRS. However, it does not cover input coordinate formats, precision, edge cases, or any output details, so disclosure is partial.

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 one compact, front-loaded phrase that communicates the operation, output concept, and offline behavior without filler. 'MGRS Grid:' is slightly redundant, but this is minimal and does not hurt clarity.

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 description gives the conversion direction and an offline hint, but an agent cannot reliably know how to format the q parameter. There are no usage examples or parameter notes, and with 0% schema description coverage, the q input format is a significant gap.

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 input schema only provides a string parameter q with a default of '' and no description. The description adds semantic meaning by identifying q's payload as lat/lon data, but it does not specify the expected string format, such as comma-separated or space-separated coordinates.

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 states a precise conversion: 'Lat/lon → MGRS military grid reference'. The arrow communicates the operation, and the result is clearly identified as an MGRS military grid reference. This distinguishes it from sibling coordinate-format tools like geohash, pluscode, and maidenhead.

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 clearly implies when to use the tool: when an agent has latitude/longitude and needs an MGRS grid reference. It does not name alternatives or exclusions, but the explicit conversion target provides enough context to avoid obvious confusion with sibling coordinate tools.

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