convert_coordinates

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

No annotations provided, so description must disclose behavioral traits. It mentions validation but doesn't specify behavior on invalid input (e.g., error handling), rate limits, or any side effects. Minimal disclosure beyond core functionality.

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?

Single sentence is concise and includes both conversion and validation aspects. No wasted words, but could be broken into separate sentences for clarity. Suitable for a simple tool.

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?

Given only two parameters and no output schema, the description covers purpose and key formats. However, it lacks details on return values, error handling, or coordinate system assumptions, which are useful for a conversion tool.

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 coverage is 100%, so baseline is 3. Description adds 'validate coordinates' which is not in the schema, providing additional context. However, it doesn't elaborate on input format specifics beyond what schema already implies.

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?

Description clearly states the tool converts between coordinate formats and validates coordinates, which is a specific verb and resource. It distinguishes from sibling tools like add_marker or create_map, which serve different purposes.

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 explicit guidance on when to use this tool versus alternatives. However, sibling tools are clearly different (map creation, markers), so context implies usage for coordinate conversions. Lack of exclusions or prerequisites keeps it at mid-range.

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