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

No annotations are provided, so the description carries the full burden for disclosing behavioral traits. It only states the conversion action, but does not mention input format expectations, handling of invalid files, whether metadata is preserved, or any limitations. This is minimal disclosure for an unannotated 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 concise, with the core purpose stated upfront and two illustrative examples. Every sentence is informative, with no wasted words.

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 present, the description is adequate but incomplete. It covers the primary purpose but lacks input format specification and any behavioral caveats, which are important for correct invocation.

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 has one parameter 'gpx' with zero description coverage, and the tool description does not clarify whether the input is file content, a file path, or a URL. This leaves the parameter semantics ambiguous and forces the agent to guess the expected input format.

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 specific verb 'Convert' and resource 'GPS track file (GPX) to KML for Google Earth'. It includes examples of use cases and inherently differentiates from sibling tools like gpx_to_geojson, as it specifies the output format.

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 clear context with examples of when to use the tool (e.g., opening a Garmin/Strava track in Google Earth). While it doesn't explicitly exclude alternatives, the purpose and examples are sufficient to guide selection among the sibling tools.

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