census_search_variables

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the behavioral detail that it returns variable IDs for downstream use, but doesn't disclose output format, pagination, or error behavior. Given the strong annotation coverage, a 3 is appropriate.

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?

Two sentences with zero filler. The purpose is front-loaded, and the mention of census_query immediately signals the tool's role in the pipeline. Nothing extraneous.

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 search tool with three documented parameters and no output schema, the description is complete enough: it states the purpose, clarifies the return value (variable IDs), and points to the downstream tool. It could mention the max_results limit, but that's already in the schema, so the description is adequate.

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 input schema fully documents dataset, keyword, and max_results. The description adds no extra parameter semantics beyond what the schema already provides. Baseline 3 is appropriate when the schema handles all parameter documentation.

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 verb 'Search' and the resource 'Census variable names/codes', and explicitly distinguishes its purpose from census_query by noting it returns variable IDs for use with census_query. This makes it obvious this is a discovery tool, not a data retrieval tool, and differentiates it from census_population and census_query.

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?

The description implicitly establishes the usage workflow: use this tool to discover variable IDs, then use census_query to fetch data. This gives clear context on when to call it. However, it doesn't explicitly say when not to use it or mention alternatives like census_population, so it stops short of full exclusions.

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