census_search_variables

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

The description does not contradict annotations (readOnlyHint: true) and clarifies it is a search operation. However, it adds little beyond the annotation: no mention of rate limits, pagination, or other behavioral traits. Annotations already cover the read-only aspect.

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 two sentences long, front-loaded with the core action, and avoids redundancy. Every sentence adds value.

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 no output schema, the description explains what the tool does and how the output connects to census_query. It is adequate, though it could mention any default sorting or result format.

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?

All three parameters (dataset, keyword, max_results) are described in the input schema. The description adds no additional meaning beyond the schema descriptions, so baseline score applies.

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 'Search for Census variable names/codes by keyword' and explains the outcome: 'Returns variable IDs you can use with census_query'. It distinguishes from sibling tool census_query (which uses the IDs) and other search tools.

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 hints at usage by stating results can be used with census_query, and mentions discovering data in a given dataset. However, it does not explicitly state when to use this tool versus alternatives like search_datasets or other sibling search tools.

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