list_datasets

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

As a read-only listing tool, behavioral transparency is adequate. However, with no annotations, the description could mention side effects or authorization, but the simple nature of listing mitigates this gap.

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 concise at two sentences, but the second sentence about S3 uploads is off-topic for a listing tool, slightly reducing relevance.

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 simple list tool with one parameter, the description is mostly complete. However, it doesn't explain the return format or pagination, which is a gap without an output schema.

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?

The only parameter 'limit' is fully described in the schema (100% coverage). The description adds no extra meaning beyond that, so baseline score 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 that the tool lists datasets for training and evaluation. While it doesn't explicitly differentiate from siblings like 'show_dataset', the name and description make the purpose obvious.

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 like 'show_dataset' or 'create_dataset'. The second sentence about uploading S3 data is irrelevant to listing.

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