gearys_c

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

Description is minimal, adds no behavioral details beyond the name. Without annotations, the agent is left uninformed about side effects or execution context.

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?

Single sentence is short and to the point, but trades off completeness.

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 the tool's complexity (4 params, multiple siblings), the description fails to convey required inputs, output, or purpose nuances, making it inadequate for correct invocation.

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?

Description does not explain any of the four parameters (shapefile_path, dependent_var, target_crs, distance_threshold), leaving the agent blind despite 0% 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?

Description clearly states the tool computes Global Geary's C Autocorrelation Statistic, distinguishing it from siblings like morans_i and getis_ord_g.

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?

No guidance on when to use Geary's C vs alternatives like Moran's I, no context on appropriateness or prerequisites.

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