dataset_images_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's a safe read operation. The description adds no further behavioral context such as pagination behavior, rate limits, or what happens if the dataset is empty or missing. It merely restates the purpose.

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 extremely concise at one sentence, which is not overly verbose. However, it is under-specified given the complexity of the tool (8 parameters). The sentence could earn its place by providing more high-level context, but it currently lacks substance. A 3 reflects 'adequate but minimal'.

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?

Given the number of parameters (8) and the absence of an output schema, the description is insufficient. It does not explain return values, filtering behavior, or any constraints. The low schema coverage and missing output details make the tool feel incomplete for an agent to invoke confidently.

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?

With 8 parameters and only 13% schema description coverage (only 'dataset' has a description), the burden falls heavily on the tool description. However, the description does not describe any parameter semantics, leaving parameters like limit, split, offset, search, classIds, hasLabel, and includeImageUrls entirely unexplained. This severely limits an agent's ability to use the tool correctly.

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 'List images in a dataset with optional filtering,' which is a specific verb-resource combination. It distinguishes from sibling tools like dataset_export or dataset_ingest, making its purpose clear. However, it does not explicitly differentiate from other list tools like datasets_list or explore_datasets, so not a perfect 5.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools include many dataset-related operations (export, ingest, delete, list), but the description does not clarify when this specific list tool is appropriate. There is no mention of prerequisites or exclusions.

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