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

With readOnlyHint=true, the safety profile is already covered by annotations. The description adds useful behavioral context beyond that: composite scoring over four layers, per-layer components, ranked drivers, coverage, and update cadence. However, it does not disclose county-scope mechanics or other behavioral caveats.

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 three sentences with no filler. The first sentence is information-dense, the second provides use-case triggers, and the third notes update cadence. Important details are front-loaded, and 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?

The description omits how a specific county is selected: the schema has no county_fips parameter and the description never says the county comes from context or a separate selection step. For a county-level tool, this is a serious invocation gap. Otherwise, the output fields and update cadence are reasonably specified.

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 only parameter (days) has 100% schema description coverage, explaining the optional history series, 5-year limit, Gold-tier requirement, and fallback to current snapshot. The tool description adds no additional parameter-level meaning, so the baseline 3 is appropriate. It also fails to clarify how the county is specified despite claiming 'any US county'.

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 a specific action ('Returns a 0-100 agriculture and rural resilience score') and identifies the resource (US county) and the output fields (composite_score, component_scores, ranked drivers, coverage). It clearly conveys the tool's unique agricultural/rural theme, though it does not explicitly differentiate itself from sibling package tools by name.

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 explicit 'Call when' context listing concrete decision scenarios: farmland risk, agricultural stability, rural land quality, food-supply resilience, and timing farmland acquisition, lending, or supply-sourcing. It lacks explicit when-not-to-use guidance or alternative tool names, so it stops short of a 5.

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