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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it explains the three maps checked, the eligibility outcomes returned, and the geocoder fallback from Census to OpenStreetMap and FCC.

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 definition is front-loaded with the core action and avoids filler. It is denser than ideal because one long sentence packs program scope, multiple map versions, return fields, and geocoder fallback, but every clause carries relevant 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?

There is no output schema, so the description usefully names the returned eligibility results, matched address, county, place, and data sources. With annotations covering read-only/open-world/idempotent behavior and the schema fully documenting the single parameter, the definition is largely complete, though it could clarify edge cases such as malformed or ambiguous addresses.

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 100% and the single address parameter is fully documented with an example in the schema. The description reinforces that it expects one US street address but does not add meaningfully more syntax or formatting detail beyond the schema, so the baseline score of 3 applies.

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 states a specific verb and resource: checking one US street address against USDA Rural Development's ineligible-area map for single family and multifamily housing programs governing Section 538. It also names the exact eligibility outputs, including current, proposed 2020-census, and previous maps, which distinguishes it from sibling tools focused on rentals, income limits, lenders, loan listing, or loan sizing.

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 makes clear this tool checks one address for rural eligibility, but it does not explicitly say when to use it instead of sibling tools such as find_usda_rural_rentals or size_538_loan. Usage is therefore implied but not routed with alternatives or exclusions.

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