find_geographies_parsed

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

No annotations are provided, so the description must carry the behavioral load. It discloses the required input combination and the PR limitation, but says nothing about return shape, layer defaults, vintage/benchmark behavior, or error conditions for a 7-parameter query tool.

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 short sentences, zero filler. The core capability leads, the input precondition follows, and the exclusion is last.

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?

For a 7-parameter tool with no annotations and no output schema, the description covers input requirements and one exclusion but omits return content, the role of layers/vintage/benchmark, and any default or pagination 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 100%, so per-parameter meaning is already handled. The description still adds a cross-parameter constraint the schema cannot express: only 'street' is required in the schema, yet the description requires zip OR city+state alongside it. That is real added semantic value.

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 compound verb+resource: geocode a parsed US address AND return Census geographies. The word 'parsed' cleanly separates it from find_geographies_oneline and find_geographies_coordinates, and 'geographies' separates it from geocode_parsed_address.

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 input precondition (street + zip, or street + city + state) and an explicit exclusion (no Puerto Rico Urbanization/Municipio). It implies but does not name the sibling to use instead (find_geographies_oneline for unparsed input, find_geographies_pr for PR), so it falls just short of the top band.

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