Geo search

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

Annotations already declare readOnlyHint=true. The description adds valuable behavioral context: it reports available=false if the PostGIS extension is not installed, which is beyond what annotations provide. It does not contradict 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?

The description is extremely concise with two sentences. The core action is front-loaded, and every sentence adds value without redundancy.

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?

Despite the tool having 7 parameters (5 required) and an output schema, the description does not explain the output format, error conditions beyond extension missing, or any additional behavioral details. The low schema coverage combined with a terse description leaves it incomplete for a spatial search tool.

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 only 14% (only the 'database' parameter has a description). The tool description does not explain the meaning or constraints of the other required parameters (schema, table, column, longitude, latitude) nor does it clarify the 'limit' default. The description fails to compensate for the low schema coverage.

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 tool's function: 'Find the rows nearest to a lon/lat point by PostGIS distance.' It uses a specific verb ('Find') and resource ('rows nearest to a lon/lat point') and differentiates from sibling search tools by mentioning 'PostGIS distance' and the extension dependency.

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 when nearest spatial search by PostGIS distance is needed, and notes that it reports available=false if the extension is missing. However, it does not explicitly state when to use this over other spatial or search tools, nor does it provide exclusion criteria or alternatives.

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