search_census_places

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

With no annotations, the description carries full burden. It discloses a crucial behavioral limitation: 'the SDK returns a single page of places per call and does not expose pagination controls, so the name filter only sees that page.' It also states the result cap ('Returns up to 50 results') and data source, providing comprehensive behavioral context.

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: purpose, important limitation, alternative, parameter explanation, return info, and source. Every sentence adds value, and the critical caveat is highlighted with 'IMPORTANT' for visibility.

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 no annotations and a minimal schema, the description covers all essential aspects: what it does, its parameters, its limitations, when to use an alternative, and result size. The presence of an output schema obviates the need to detail return fields, making this complete.

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 0%, and the description fully compensates by explaining both parameters: 'level is the geography level from explore_census_geographies (e.g. state, county, place)' and 'query is an optional substring filter on place name.' This adds meaning beyond the bare type declarations.

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: 'List US Census places at a given geography level, optionally filtered by name (case-insensitive).' This is a specific verb+resource+scope, and it distinguishes itself from the sibling get_census_place by framing this as a list/search operation.

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 provides when and when-not to use the tool: 'For large levels like tract (73k+ places), if you already know the FIPS code use get_census_place directly instead.' This names a concrete alternative and gives clear context for selection.

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