Resolve US Place to Population, Area Tier, and Multiplier Base

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

No annotations exist, so the description carries full burden. It discloses the free Census API, no key required, and explains the geocoding and fetch process. However, it lacks explicit error handling details (e.g., when city is not found).

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?

The description is well-structured with the main action upfront, followed by return fields and usage guidance. It is slightly verbose but every sentence adds necessary information.

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?

Given the tool's complexity (6 parameters, no output schema), the description adequately explains the returned fields and their purposes (e.g., county FIPS for usaspending_award_search). Some structured output would improve completeness, but it's sufficient.

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 baseline is 3. The description adds value by explaining parameter pairs (e.g., city/state vs placeFips/stateFips) and the dryRun function, providing context beyond the schema.

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 clearly states the tool's purpose: 'Look up a US city/town/CDP via the Census geocoder, then fetch its total population from the ACS 5-year estimate.' It lists the returned fields, distinguishing it from siblings like adv_estimate.

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 advises to 'Use this BEFORE adv_estimate when sizing an enforcement universe or running a restaurant research workflow against an unfamiliar city.' This provides clear when-to-use and when-not-to-use context.

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