nearest_point_on_geometry

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

The description mentions the underlying implementation (shapely.ops.nearest_points) and the return format (dictionary with status, message, and WKT point). However, it lacks detail on error handling, behavior with invalid geometries, or performance considerations. With no annotations, the description carries full burden and provides moderate transparency.

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 concise at three sentences, with a clear front-loaded purpose and structured Args/Returns sections. Every sentence adds information, though the Args/Returns section partially duplicates schema information.

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 explains the return format (dictionary with status, message, and nearest point as WKT) and the tool's simple parameter requirements. With an output schema present, the description is sufficiently complete for this straightforward operation, though it could mention edge cases.

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 description explains that geometry1 is the first geometry (e.g., a point) and geometry2 is the second geometry, both as WKT strings. Given the schema coverage is 0%, the description adds minimal extra meaning beyond what the schema provides. It does not specify valid WKT formats 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 states that the tool finds the nearest point on geometry2 to geometry1, using the specific verb 'Find' and resource 'nearest point on geometry'. It distinguishes itself from sibling tools like 'snap_geometry' or 'project_geometry' by focusing on the nearest point operation.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, limitations, or scenarios where this tool is preferred over others like 'project_geometry' or 'calculate_geodetic_distance'.

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