geom_transform

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: distances are true ground metres, buffering uses an azimuthal equidistant projection (avoiding degree-based distortion), and concave vs convex hulls have distinct use cases. This goes beyond what annotations provide.

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 front-loaded with a one-sentence summary, then provides necessary details on projection and hull selection. The second paragraph is somewhat lengthy but explains a common pitfall (degree-based distortion) that saves real trouble. Overall it is tight and purposeful, with no filler.

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 tool supports seven operations, but the description only elaborates on buffer and hulls. Centroid, simplify, repair, and bbox are not given any specific behavioral or usage context. Since an output schema exists, return values are covered, but some operations remain under-described for an AI agent to choose among them confidently.

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 the baseline is 3. The description adds meaningful nuance beyond the schema: it explains that distances are true ground metres, that the ratio scale is steeply non-linear, and that distance_m is applied in metres for both buffer and simplify. This enhances understanding of how parameters behave in practice.

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 first sentence 'Reshape a geometry: buffer, simplify, hull, centroid, repair or bounding box' clearly states a specific verb (reshape) and the resource (geometry), and lists the supported operations. It does not explicitly differentiate from sibling tools like geom_measure or geom_overlay, but the operation list makes the tool's scope evident and distinct enough.

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 gives implicit usage guidance by naming the operations, but it never explicitly says 'use this tool when you need X, use geom_measure when you need Y'. There is useful internal guidance on choosing concave_hull vs convex_hull, but no direct comparison to sibling tools or exclusions, so it remains at an implied level.

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