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

With no annotations, the description fully discloses important behaviors: points become waypoints, lines/polygon rings become tracks, and non-name properties are dropped. It explains the rationale (GPX lacks polygon types and attribute tables), providing transparent insight into data transformation and potential data loss.

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 well-structured, front-loaded with the primary function, and uses examples to illustrate usage. Each sentence adds value: conversion rules, geometry behavior, and property dropping are all relevant. It is concise without being overly terse.

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 conversion tool with one parameter and an output schema, the description covers all necessary aspects: the conversion process, geometry-type mapping, and data loss caveats. It does not need to explain return values since an output schema exists. The description is complete and self-sufficient.

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 schema only defines 'geojson' as a string without a description (0% coverage). The description effectively implies the parameter contains GeoJSON data, reinforced by the tool's purpose and examples. While it doesn't explicitly state the expected format (e.g., WGS84), the meaning is unambiguous for a single-parameter tool.

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 GeoJSON to a GPX file, with examples like 'export this as a GPS track' and 'GeoJSON to GPX for my Garmin'. It also specifies geometry handling (points to waypoints, lines/polygons to tracks), which distinguishes it from other conversion tools and clarifies its exact scope.

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 provides concrete usage examples and implies when to use it (GPS track export, Garmin devices). It also mentions limitations like dropped properties and polygon handling, but does not explicitly contrast with alternative formats (e.g., KML, CSV) or state when not to use it. This is clear context but lacks direct exclusions.

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