dol_list_datasets

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

Discloses client-side filtering, throws on 5xx, handles schema drift, explains pagination and totalAvailable behavior. Adds value beyond readOnlyHint and openWorldHint annotations with honest verification.

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?

Well-organized with core purpose first, then details, return format, and error handling. Slightly verbose but every sentence provides unique value; minor redundancy possible.

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?

Covers all essential aspects: input, filtering behavior, return structure, pagination, error modes, and connection to sibling tool. No output schema, but return format is documented inline.

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?

Enriches every parameter beyond schema descriptions: default/max for limit, examples for query, client-side nature for agency, pagination hint for offset. Coverage is 100% and description adds concrete, actionable detail.

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?

Clearly states it lists the DOL Data API v4 dataset catalog, identifies it as the machine inventory of enforcement/statistics datasets, and distinguishes itself from dol_get_dataset by noting keyless access.

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?

Explicitly describes when to use (catalog listing) and how to connect results to dol_get_dataset. Implicitly excludes other tools through sibling context, but lacks explicit 'when not to use' statements.

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