list_datasets

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

With no annotations provided, the description must carry the full burden of disclosing behavior. It only mentions 'bounded pagination' without specifying the bound, and it omits details about default page/page_size, ordering, return format, or required permissions. This is a significant gap for a tool with no annotation support.

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 a single, front-loaded sentence with no fluff. Every word contributes to the core meaning, and it is appropriately sized for the tool's simplicity.

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?

This is a minimal tool with 3 optional parameters and no output schema. The description gives enough to know its basic function but leaves out details like the return shape (what dataset fields are returned) and defaults for pagination. It is adequate but not rich; slightly more context would make it complete for an agent.

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%, so the description must compensate. It does add some meaning by clarifying that 'search' is a name search and that pagination is bounded, but it does not explain the semantics of page/page_size (e.g., zero-indexing, default values, maximum page size). The parameter usage remains under-specified.

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 clear action ('List datasets'), identifies the resource (datasets), and distinguishes it from sibling list tools (e.g., list_saved_queries, list_dashboards) by naming the target resource. It also mentions two key features (optional name search and bounded pagination), making the purpose unambiguous.

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 provides clear context: this tool is for listing datasets, optionally filtered by name and paginated. It does not explicitly state when not to use it or suggest alternatives, but the context is sufficient for a simple list operation.

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