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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the generic-query scope and a SoQL reference link, but does not disclose response variability, pagination behavior, or error handling. With strong annotations, the added behavioral context is adequate but not rich.

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?

Three concise, front-loaded sentences. The first sentence states the purpose, the second gives usage routing, and the third provides the necessary reference link. No filler or redundant restatement of the schema.

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 generic query tool, the description covers purpose, usage conditions, dataset ID format, and query-language reference. It could add an example or note that the output schema varies by dataset, but the full parameter documentation and SoQL reference reduce the need for more.

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 baseline is 3. The description adds value by identifying the dataset parameter as a '4x4 Socrata ID' and highlighting the 'where-clause' as central, while the linked SoQL reference provides syntax semantics for where, select, order, and limit beyond the schema.

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: 'Generic SoQL query against any data.cdc.gov dataset.' It also distinguishes itself from sibling tools by explicitly saying to use it 'when none of the curated tools fit,' which prevents confusion with the many cdc_* siblings.

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 gives an explicit usage condition: 'Use this when none of the curated tools fit.' This clearly defines the catch-all role and implies the when-not case, namely when a curated CDC tool is applicable. This is sufficient routing guidance.

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