list_datasets

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

Annotations already cover read-only/idempotent safety, but the description adds real behavioral context: scoping is per-user, and there is deliberately no server-side status filter, so the owner sees items in every approval state. That is exactly the kind of non-obvious behavior an agent needs before interpreting empty or full results.

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 short sentences, with the scope and ownership constraint front-loaded and the filter tip last. The 'Use type to filter' sentence partially duplicates the schema's own enum description, a minor redundancy.

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 no output schema and no annotations about result shape, the description does not say what a returned item looks like or whether pagination metadata accompanies results. The ownership/status nuance is covered well, but the return contract and paging behavior are left implicit.

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 coverage is only 33%: only 'type' is documented in the schema, and the description merely restates that enum. The pagination parameters 'skip' and 'limit' (defaults 0/20, max 500) are never explained, so the description does not compensate for the coverage gap.

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?

States a specific verb and resource ('List the caller's own datasets and/or models') and disambiguates the resource with 'uploaded or generated'. It is clear an agent can distinguish it from get_dataset, though it never names the sibling explicitly.

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?

'Use type to filter to just dataset or just model' gives concrete invocation guidance, and the per-user/ownership note tells the agent when this listing will and won't surface items. It stops short of naming alternatives such as get_dataset for individual retrieval.

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