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

With no annotations, the description does real work: it names the auth mechanism (api_key or Bearer, tied to a paid pass), states a 4.5 MB inline size limit, and describes the success path with a download_url fallback for large results plus an error shape including `pairs`. It omits cost implications, whether conversion is lossy, and any rate limits.

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 format enumerations earn their place, but the opening marketing preamble about the 24-hour/7-day/monthly pass is noise that delays the actual purpose. The remainder is a dense run-on that front-loads pricing before function.

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 7-parameter converter with an output schema, the description covers the inputs, format matrix, CRS handling, size limit, and error contract. An agent has enough to invoke it correctly; the only meaningful gap is that return values are described redundantly given the output schema already exists.

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 0% and the description compensates thoroughly: it enumerates the valid `to` targets (which the schema provides no enum for), explains `source` values for mapinfo-tab and filegdb, defines when `source_epsg` is needed (projected CSV / shapefile without .prj), and describes `target_epsg` reprojection plus the base64 input constraint. All seven parameters get meaningful semantics.

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?

States a specific verb and resource ('convert one GIS file between formats') and enumerates the accepted input and output formats, so the agent knows exactly what it does. However it never names the many dedicated siblings (kml_to_geojson, shapefile_to_gpx, bundle_migrate_convert) or explains why this generic converter exists alongside them.

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?

Usage is implied: use it to convert between formats, and use `source` when the zip is MapInfo TAB or FileGDB. But there is no explicit when-to-use-this-vs-alternatives guidance despite ~15 sibling conversion tools that overlap heavily, leaving the routing decision to inference.

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