unary_union_geometries

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

No annotations provide behavioral hints. The description does not disclose whether the tool handles overlapping areas, input order, or invalid geometries. Does not mention that it is a unary operation.

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?

One sentence, no waste, but it is too brief to be fully useful while still being minimally viable.

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 no annotations and an output schema, the description should clarify return value or side effects. It does not explain the unary nature nor differentiate from sibling 'union'. Incomplete for a geometry operation tool.

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?

Parameter 'geometries' lacks description in schema (0% coverage). The description adds no information about expected format (e.g., GeoJSON, WKT) or constraints.

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 identifies the action (union) and resource (multiple geometries), and implicitly distinguishes from binary union via sibling 'union'. However, it could specify input format more explicitly.

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?

No guidance on when to use this tool vs alternatives like 'union' or 'difference'. Missing context about when a unary union is preferred over pairwise operations.

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