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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety and network profile is covered. The description adds the SoQL reference link and the pass-through nature, but says nothing about rate limits, error behavior on invalid dataset IDs, or result shape beyond the schema's limit cap.

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 short sentences, front-loaded with the core purpose, then the usage condition, then the reference link. Efficient, though the SoQL URL sentence is a mild redundancy given the schema already names SoQL clauses.

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 fallback query tool, the description plus 100%-covered schema and read-only annotations give an agent everything needed to invoke it correctly. No output schema exists, and the description needn't explain return values for a raw SoQL pass-through.

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 all five parameters (including limit default/cap and example clauses) are already documented in the schema. The description only restates that a 4x4 Socrata ID and a where-clause are accepted, adding essentially nothing beyond the structured fields.

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?

States a specific verb (query) and resource (any data.cdc.gov dataset) and explicitly positions itself as the generic fallback against the many curated cdc_* siblings. An agent can tell it apart from the curated tools without opening any 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?

"Use this when none of the curated tools fit" gives a clear conditional that routes the agent here only as a fallback. It stops short of naming specific curated alternatives, but the alternative category is explicit and unambiguous.

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