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

With no annotations provided, the description carries the full burden. It discloses coverage scope (transmission only), data source, no-key requirement, and the return format. While it does not mention rate limits or real-time vs. cached data, the transparency is good for a safe read-only tool.

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 4 sentences, front-loading the purpose. Every sentence adds value: data source, scope, disclaimer, and return structure. No redundant or unnecessary 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 provides essential context: data source, coverage limitations, and return fields. However, it lacks details like search radius or what the 'count' field represents. Given the output schema exists (implied by the described JSON), the description is fairly complete but could be enhanced.

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 schema has 2 required parameters (lat, lon) with 0% description coverage in the schema. The description does not add any meaning to these parameters, such as coordinate system (e.g., WGS84) or expected format. This is a significant gap for an agent to correctly invoke the tool.

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 assesses natural gas pipeline proximity at a US point, specifies the data source (EIA/HIFLD, 32,892 segments), and distinguishes it from proprietary 'call before you dig' data and local distribution lines. This makes the purpose specific and well-differentiated from sibling tools.

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 explicitly states when to use (for major transmission pipelines) and when not to use (not for local distribution, not a substitute for calling 811). It provides clear usage boundaries but does not explicitly compare to sibling tools like assess_grid_exposure or assess_wildfire_risk.

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