datasets_list

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

The description mentions 'read-only', which is a behavioral trait, but with no annotations provided, the description carries full burden and does not disclose auth needs, rate limits, or any potential side effects beyond reading.

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 short and to the point, though the first two sentences are slightly redundant ('List stored scraped datasets' and 'Lists available read-only...'). It conveys the core purpose efficiently.

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?

The description does not explain what the output looks like (e.g., fields returned) and does not clarify the purpose of the enum value beyond hinting. For a tool with no output schema, more detail on return structure would improve completeness.

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?

There are no parameters, and schema coverage is 100% trivial. The description adds no parameter information (none needed), so baseline 4 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 clearly states the verb 'List' and the resource 'stored scraped datasets', with a specific enum value ('google-map-businesses') that differentiates it from sibling tools like datasets_google_map_businesses_item.

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 this tool is the entry point to get dataset IDs before using other dataset tools, but it does not explicitly contrast with alternatives or provide when-not-to-use guidance.

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