merge_gpd

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

No annotations are provided, so the description carries the full burden. It explains the operation type (merge based on attributes), preserves left geometry, and writes to output_path. However, it lacks details on potential side effects, error handling, or prerequisites like CRS alignment.

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 fairly concise yet includes structured parameter docs. It doesn't waste words, though the mismatch in parameter names adds unnecessary confusion. It could be slightly tighter by aligning with schema names.

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?

Given the tool's complexity (merge with multiple join options) and schema with only 3 params, the description's parameter mismatch and lack of details on join keys (on, left_on, etc.) leave gaps. An output schema exists, so return values aren't needed, but prerequisites like attribute existence are missing.

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 input schema has 3 parameters with zero description coverage. The description adds meaning by describing parameters like left_shapefile_path and how, but these names mismatch the schema (shapefile1_path, shapefile2_path). The additional parameters not in the schema further complicate understanding, making the description less useful for the actual tool interface.

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 it merges two shapefiles based on common attribute columns and distinguishes it from a spatial join. However, the parameter names in the description (left_shapefile_path, right_shapefile_path) do not match the actual schema (shapefile1_path, shapefile2_path), which could cause confusion.

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 explicitly notes it performs a database-style join, not a spatial join, which hints at appropriate usage compared to sibling spatial join tools. However, it does not provide explicit when-to-use or when-not-to-use guidance, nor mention alternatives like sjoin_gpd.

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