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

With no annotations provided, the description carries the full burden. It clearly states the conversion behavior and adds context about typical WKT sources. It does not discuss error handling or edge cases, but for a pure string-format conversion this is a minor gap.

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 a single sentence that front-loads the core transformation before adding contextual examples. It is concise overall, though the parenthetical examples are slightly redundant with the name and could be trimmed without losing 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?

This is a low-complexity tool with one required parameter and an output schema present. The description fully explains the input format, common sources (PostGIS/SQL), and the transformation purpose, making it sufficiently complete for an agent to select and invoke the tool correctly.

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 only defines a 'wkt' string with 0% description coverage. The description compensates by explaining what WKT is (the format PostGIS/SQL geometry columns print by default) and provides a 'POLYGON(...)' example, giving the agent enough semantic understanding of the parameter.

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 opens with 'Convert a WKT (Well-Known Text) geometry string ... to GeoJSON', clearly specifying the verb, input resource, and output format. This distinguishes it from sibling tools like geojson_to_wkt (opposite direction) and csv_to_geojson (different input format).

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 concrete usage context by noting WKT is the format PostGIS/SQL geometry columns print by default and gives example prompts like 'this came from a PostGIS query' and 'parse this POLYGON(...) string'. It does not explicitly name alternative tools or state when not to use it, but the context is clear.

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