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

With no annotations, the description carries the burden of disclosure. It accurately states the conversion action and the return JSON structure including base64 ZIP and warnings. However, it does not detail any limitations (e.g., shapefile field name restrictions, geometry type handling, or CRS assumptions) that could be relevant for an agent.

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 two sentences that front-load the main action and include useful example queries. Every sentence adds value: the first explains the conversion and target audience, the second specifies the return format.

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 is mostly complete. It includes the output structure and practical usage context, but lacks explicit input format specification and potential conversion constraints. The output schema exists, so return values are partly covered, but the description supplements it well.

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 0% description coverage and the only parameter is 'geojson' with type string. The description does not clarify whether the input is raw GeoJSON text, a file path, or a URL. It only repeats that the tool converts GeoJSON, adding little beyond the parameter name itself.

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 'Convert GeoJSON to an Esri Shapefile ZIP' with a specific verb and resource. It distinguishes from siblings by specifying the target format and mentioning ArcGIS Pro/QGIS, which are not relevant to CSV or KML conversions.

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 on when to use the tool through example user requests like 'I need a shapefile for ArcGIS Pro' and 'convert for QGIS import'. It does not explicitly name alternatives or exclusions, but the use cases make the intended scenario evident.

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