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

Annotations already establish read-only, idempotent, non-destructive behavior; the description adds 'no auth required' and the per-portal resource API nature, plus the JSON return format. No contradiction with annotations.

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 dense sentences front-load the operation and clauses before the prerequisite and endpoint details. No wasted words; all information earns its place.

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?

With output schema present and annotations covering safety, the description provides the missing workflow (search first, get columns from metadata), example domain, and auth status. It is complete enough for an agent to invoke correctly; minor absence of explicit pagination guidance is covered by schema on limit/offset.

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 covers all 8 params with descriptions and examples. The description adds the SoQL clause mapping and the requirement to consult socrata.dataset_metadata for column names, but this is supplementary; baseline 3 due to full schema coverage.

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 names an explicit verb-resource pair ('Run a SoQL query against a specific dataset's actual data rows') and differentiates from sibling search/detail tools by emphasizing actual data rows. It lists the supported SoQL clauses, leaving no ambiguity about scope.

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?

It tells the agent to call socrata.dataset_search first to obtain domain and dataset_id, and points to socrata.dataset_metadata for column names. It doesn't spell out when not to use this tool vs socrata.datasets.detail, but the prerequisite and clause context effectively route invocation.

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