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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is covered. The description adds useful context beyond annotations: it identifies the data source (live Census ACS, 118th Congress) and describes the fallback mode when cd is omitted. It does not mention rate limits or staleness of ACS data, but the added source and scoping context is solid.

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?

Front-loaded with the core purpose and data fields, then use cases, then the fallback behavior. Slightly list-heavy in the data-field enumeration, but every sentence earns its place and there is no filler.

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?

Covers purpose, data returned, use cases, and the cd-omission fallback, which is what an agent needs for a two-parameter read-only tool. No output schema exists, so the description appropriately enumerates return fields. It could note data-freshness expectations for live Census data, but overall it is complete for the tool's complexity.

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%: both cd and state are fully documented in the schema, including the 1- or 2-digit format for cd and the 2-letter state code. The description restates the cd omission behavior but adds no new format, validation, or semantic detail beyond the schema. 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, resource, and scope: returns veteran demographics for a congressional district using live Census ACS data, and explicitly lists the data fields produced. This distinguishes it from siblings like get_tract_demographics and get_state_dashboard by naming the congressional-district unit and the veteran-specific metrics.

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?

Explicitly when to use (congressional staff fact-sheets, foundation grant proposals, local journalism, advocacy targeting) and gives a concrete fallback behavior when cd is omitted ('returns ALL districts in the state ranked by veteran count'). The alternative behavior is spelled out rather than left to inference.

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