GIS MCP Server

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

No annotations are provided, so the description carries full burden. It mentions the tool exports files and returns a dictionary, but omits critical behavioral details: whether it overwrites existing files, requires specific permissions, handles errors, or has performance/rate limits. The description is insufficient for a mutation tool with no annotation coverage.

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 with clear sections (Args, Returns) and uses efficient sentences. However, the 'Args' and 'Returns' labels are redundant with structured fields, slightly reducing conciseness.

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?

With no annotations, 3 parameters (0% schema coverage), and an output schema, the description is moderately complete. It covers parameters and return format, but lacks behavioral context for a file-writing tool (e.g., overwrite behavior, error handling). The output schema helps, but gaps remain.

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 description coverage is 0%, but the description compensates by explaining all three parameters: 'gdf_path' (input file path), 'output_path' (export location), and 'driver' (optional format with examples). It adds meaning beyond the bare schema, though it could detail driver options or path requirements further.

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 action ('Export a GeoDataFrame to a file') and resource ('GeoDataFrame'), with examples of output formats ('Shapefile, GeoJSON, GPKG, etc.'). It distinguishes from sibling tools like 'read_file_gpd' (import) and 'write_raster' (raster-specific).

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 implies usage for exporting geospatial data, but lacks explicit guidance on when to use this tool versus alternatives (e.g., 'write_raster' for raster data, 'save_results' for non-geospatial output). No prerequisites or exclusions are mentioned.

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