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 profile is covered. The description adds genuine value beyond that: the underlying data source and vintage (ACS 2020–2024 5-year), the exact fields returned, and the dual input modes. No gaps that would mislead an agent.

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, followed by usage context and input modes. The illustrative quoted example ('Your area has X veterans...') is slightly verbose but earns its place by showing the intended output framing.

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 must carry the return-value burden — and it does, enumerating all reported metrics (population, 18+, veteran count/percentage, poverty count/percentage, unemployment, median income). Combined with the data vintage and input modes, an agent has everything needed to call and interpret it.

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%, so the baseline is 3. The description adds meaning by clarifying that FIPS codes and resource_id are alternative input modes ('Accepts FIPS ... OR a resource_id'), which the per-parameter schema text does not make explicit about mutual exclusivity.

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 (Get), resource (Census ACS 2020–2024 5-year demographics), and scope (a specific census tract), then enumerates the exact metrics returned. The tract-level granularity clearly differentiates it from sibling tools like get_zip_overview, get_congressional_district_veterans, and get_housing_context.

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?

Gives a concrete usage context: when you have a resource location, or want to contextualize advice for a veteran. However, it never names alternative tools (e.g., get_zip_overview for coarser granularity) or states when NOT to use it, so routing among the many geography tools is left partly to inference.

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