geometry_to_geojson

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

No annotations are provided, so the description carries full burden. It mentions using shapely.geometry.mapping and the return structure, but does not disclose error behavior, performance characteristics, or limitations. Adds some context but not deeply transparent.

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, with a clear first sentence stating the purpose, followed by structured Args/Returns. No redundant information, every sentence earns its place.

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 that there is an output schema (context signal true), the description's mention of 'Dictionary with status, message, and GeoJSON representation' adds some completeness. However, it does not cover possible status values or error messages. For a simple tool with one parameter, it is adequate but could be more thorough.

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 input schema has 0% description coverage, so the description must compensate. It specifies that the geometry parameter is a WKT string, adding meaning beyond the schema's 'string' type. This is helpful for correct invocation.

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 the conversion from Shapely geometry (WKT) to GeoJSON. This is a specific verb-resource pair and distinguishes from sibling tool geojson_to_geometry which does the inverse.

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 implies usage for converting geometry formats, but does not explicitly state when to use this tool versus alternatives like geojson_to_geometry or other geometry manipulation tools. No exclusions or context provided.

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