census_search_variables

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

The annotation readOnlyHint=true already discloses the safety profile. The description adds valuable context: it returns variable IDs, not data values, and that these IDs can be used with census_query. This goes beyond what annotations provide and does not contradict them.

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 three concise sentences, each earning its place: the first states the core action, the second explains the purpose, and the third explains the output and integration with census_query. There is no redundant or vague wording.

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 full schema coverage and no output schema, the description adequately covers the core purpose, the output type, and the follow-up use. It does not describe result format or pagination, but this is acceptable given the tool's simplicity and the schema covering parameters.

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?

The input schema already provides 100% description coverage, including examples for dataset and keyword. The description adds no additional parameter semantics beyond what the schema documents, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Search for Census variable names/codes by keyword.' It clearly distinguishes itself from the sibling tool census_query by stating it returns variable IDs for use with that tool, effectively differentiating a metadata discovery tool from a data query tool.

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 implies when to use this tool by noting 'Helps discover what data is available in a given dataset' and explicitly connects the workflow: 'Returns variable IDs you can use with census_query.' This provides clear context but does not explicitly state exclusions or alternative tools beyond the implied census_query.

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