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

Annotations already cover the read-only, idempotent, non-destructive and open-world profile, so the description's job is the data-quality story — and it delivers: source URLs, verification dates, explicit unverified status, headline exclusions, separate conditional-income totals, and the caveat that income is unknown and conditional amounts merely illustrate the below-80% AMI tier. This is substantive context an agent cannot get from the annotations, though it omits any mention of rate limits, cost, or caching.

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?

Five dense sentences, none of which is padding — each discloses a distinct output or data-provenance property. Readability suffers somewhat from compressed jargon ('up-to flags', 'sourced financing'), and the most decision-relevant caveat (screening only, not final eligibility) is buried at the end rather than front-loaded.

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 an output schema present and a single simple parameter, the description is close to sufficient: it explains what the response excludes and how conditional amounts should be read, which the output schema alone likely cannot convey as intent. The only real gap is the absence of any routing information relative to the sibling tools in this workspace.

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?

One parameter with 0% schema description coverage; the schema only enforces the 5-digit pattern. 'ZIP-level programs' implies the zip scopes results to a single ZIP, but the description adds no detail on accepted formats, whether surrounding ZIPs are included, or what an invalid/missing ZIP yields.

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 verb+resource ('Screen ZIP-level programs') and closes with a clear scope boundary: 'screening only, not a final eligibility determination.' It does not mention any of the sibling tools (get_program_status, resolve_utility, get_energy_profile), so an agent gets no explicit differentiation among them.

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?

Usage is implied rather than stated: the 'screening only, not a final eligibility determination' line tells the agent when the output is and isn't sufficient for a decision. There is no explicit when-to-use versus the three siblings, and no prerequisites (e.g., whether resolve_utility or get_energy_profile should run first) are given.

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