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

With no annotations provided, the description itself must disclose behavioral traits. It does state that the tool 'Returns the KML as plain text', which is a useful behavioral detail about output format. However, it does not mention any limitations, edge cases, or error handling. The disclosure is adequate but minimal.

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, front-loaded with the core action, and every sentence earns its place. The parenthetical examples are valuable usage illustrations without bloating the text. It is well-structured and easy to parse.

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 one-parameter conversion tool, the description covers the main aspects: what it does, when to use it, and the output format. An output schema exists, so the description does not need to detail the KML structure. Minor gaps include not mentioning that the input should be a GeoJSON string in a specific syntax, but overall it is sufficiently complete.

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 parameter 'geojson' has zero schema description coverage, and the description fails to add meaningful semantics beyond the parameter name. The phrase 'Convert GeoJSON' merely restates the parameter's purpose, providing no additional guidance about expected format, examples, or constraints. The description should compensate for the low schema coverage but does not.

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 a specific action: 'Convert GeoJSON to KML'. It also includes concrete use-case examples ('open this in Google Earth', 'make this viewable in Google My Maps') that distinguish this from other format converters. The purpose is unambiguous and differentiates from sibling tools like geojson_to_csv or kml_to_geojson.

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 explicit example user requests ('open this in Google Earth', 'GeoJSON to KML', 'make this viewable in Google My Maps') that signal when to use this tool. It does not, however, mention when not to use it or name specific alternative tools, so it falls short of full usage guidance.

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