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

With no annotations, the description fully discloses behavior: it auto-repairs invalid geometry, returns a structured JSON with fields like fixed_count, stats, envelope, and the possibly fixed geojson. No hidden side effects are implied.

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?

Three sentences with no fluff. The first sentence front-loads the core action and list of operations. The second sentence provides usage context, and the third details the return structure. Every sentence adds value.

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?

The description lists the return fields and notes the input may be auto-fixed. It does not cover error handling or invalid input behavior, but given the presence of an output schema (implied), the description is largely complete for typical use.

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 single parameter 'geojson' has 0% schema description coverage. The description adds context by using the term 'GeoJSON', making it clear the parameter expects a GeoJSON string. However, it does not specify expected format or constraints beyond that.

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 explicitly states it performs validation, auto-repair, stats (area/length/vertices), and bbox envelope in one call. It clearly distinguishes itself by mentioning it replaces four separate sibling tools (validate_geojson, fix_geometry, geometry_stats, envelope_geojson).

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 says 'replaces 4 separate calls', providing clear guidance that this tool is a combined alternative. The sibling list includes those four tools, so the agent can infer when to use this versus the individual ones.

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