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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is low. The description goes beyond that by disclosing the join logic (resource directory × ACS 2020–2024 5-year tract demographics) and the dataset backing (84,365 tracts, 50 states + DC + PR), which tells the agent about scope and freshness.

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?

Three sentences, front-loaded with the purpose and then the mechanics and data provenance. The final coverage sentence borders on marketing but usefully signals geographic scope; overall it is tight, though it could be marginally leaner.

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?

With no output schema, the description steps in to describe the key return fields (gap_score, poverty %, median income, FIPS codes), so an agent knows what comes back. For a read-only query tool over 4 optional params, this is essentially complete, missing only pagination/ordering behavior.

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 coverage is 75%, with state, min_veterans, and max_resources already documented in the schema; only limit lacks a description. The description explains the gap concept (few or no resources) that underpins min_veterans/max_resources but does not add syntax or interpretation beyond the schema, so the baseline 3 is appropriate.

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?

States a specific verb (find) and resource (census tracts where veterans live but few resources serve them), and defines the 'service desert' concept precisely. An agent can distinguish it from siblings like get_tract_demographics (raw demographics) and find_high_housing_burden_tracts (a different gap metric) without opening any schema.

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?

Frames the use case clearly — 'highest-impact targets for outreach, partnership development, and grant proposals' — telling the agent what downstream task this serves. However, it never names when NOT to use it or which sibling to prefer for a related question, so the alternative-routing guidance is absent.

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