Create Census Peer Cohort (Fast)

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that it uses only Census ACS data across about 75 cities and lists comparison dimensions, but it does not state whether it writes or stores anything, what permissions are needed, or what the return format looks like.

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 front-loaded with purpose and speed, then lists compared dimensions and criteria, and ends with the alternative. Every sentence earns its place and there is no waste.

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 simple three-parameter read-style tool with 100% schema coverage and no output schema, the description is nearly complete: it covers purpose, data source, comparison criteria, and the alternative tool. It leaves minor gaps around return shape and side effects, but not enough to prevent correct invocation.

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%, so the schema already documents city, criteria, and cohortSize. The description lists the criteria enum values and comparison dimensions, adding some context, but does not add syntax or default behavior beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: find peer cities based on Census demographic data. It distinguishes this fast, Census-only tool from the richer multi-source sibling create_full_cohort. An agent can identify its scope and purpose without opening the schema.

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?

It explicitly says to use this for quick demographic peer matching and directs the agent to create_full_cohort for richer multi-source comparison. The when-to-use and alternative conditions are stated plainly.

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