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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the exact payload composition, though it says nothing about truncation, response size, or behavior when a ZIP is outside covered data.

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?

Single dense sentence with the input constraint front-loaded and the return components enumerated compactly. The long return list is justified because there is no output schema, though it reads as a catalog rather than prose.

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 correctly carries the burden of describing the return payload in detail, and annotations cover the safety profile. It is nearly complete, missing only edge-case behavior (invalid/uncovered ZIP, radius interaction, result limits) that an agent might need.

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%: the zip pattern and the radius default/max are fully documented in the schema. The description restates the 5-digit ZIP input but adds no new meaning, and never mentions radius or its effect on the resource search.

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 names a specific input (5-digit US ZIP) and enumerates exactly what the tool aggregates: nearest resources, resource-type counts, tract demographics, CDC PLACES, ACS rent burden, benefits and crisis links. This composite ZIP-scoped scope clearly separates it from siblings like search_by_city, get_tract_demographics, or search_veteran_resources.

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?

"Useful when only a ZIP code is known" gives a clear selection condition that implicitly points away from city- or text-based siblings. However, it never names an alternative tool or states when NOT to use this one (e.g. when a city or address is available), leaving the routing decision partly to inference.

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