GeoJSON utilities

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds some real behavior detail — validation checks structure/coordinate ranges/closed rings, and simplification preserves altitude — but says nothing about output shape, error reporting, or vertex-count effects. Modest added value over the annotations.

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?

A single dense sentence with three parallel clauses and no filler; it is front-loaded with the verbs. It is appropriately sized for the tool, though the heavy compression means the parentheticals carry a lot of implicit meaning.

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 four-parameter, multi-operation utility with no output schema and full schema coverage, the description covers all three modes adequately. It omits the return/error format of validate, but that is a minor gap against a read-only, closed-world utility whose safety is already declared.

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 100%, so parameters like toleranceKm, points, and geojson are already fully documented in the schema, including units and defaults. The description adds no syntax or format meaning beyond that, so the baseline 3 applies.

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 names three concrete operations (validate, simplify, convert) with specific detail on each — coordinate ranges, closed rings, altitude preservation, and points-to-FeatureCollection. This maps directly onto the operation enum, so an agent can immediately tell what the tool does without opening the schema.

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 three operations are enumerated, which implies which one to pick for a given task, but the description never states conditions, prerequisites, or exclusions (e.g. when to prefer simplify over external processing). Usage is inferable rather than stated, and no alternatives are named among the geo siblings.

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