list_my_datasets

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'List' implies a read-only, non-destructive operation, but nothing is said about pagination behavior, result ordering, empty-result handling, or whether authentication is required.

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?

A single three-word sentence with zero wasted content and the operative verb front-loaded. It is efficient, though arguably too terse; the thinness is better penalized under parameter_semantics and contextual_completeness than here.

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 tool with no output schema and no annotations, the description should at least clarify return shape and pagination semantics. It provides only the core purpose and leaves everything else implicit, which is minimally viable but clearly incomplete.

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 description coverage is 0% — both 'page' and 'limit' have empty descriptions. The tool description does not compensate by mentioning pagination parameters, their meaning, or bounds, leaving agents to infer that page/limit control result paging.

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 states a specific verb ('List') and resource ('your datasets'), with the possessive 'your' establishing an ownership scope that distinguishes it from public dataset search. It is clear and comprehensible, though the differentiation from siblings like search_datasets or list_dataset_files is carried by the tool name and the word 'your' rather than explicit contrast.

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 given about when to use this tool versus search_datasets, list_dataset_files, or even the parallel list_my_kernels. The only implicit context is the word 'your,' which suggests the authenticated user's own resources, but there is no mention of prerequisites, pagination workflow, or exclusion criteria.

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