list_datasets

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

No annotations are provided, so the description carries the burden for behavioral disclosure. It adds the useful behavior of optional workspace scoping, but does not mention any other behavioral traits such as pagination, permissions, or filtering behavior beyond the workspace scope. For a simple list operation, this is acceptable but leaves some gaps.

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 sentence that is front-loaded with the action and immediately describes the optional parameter. Every word earns its place; there is no waste.

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?

The tool has one optional parameter and an output schema, so the description does not need to explain return values. The description covers the scanning behavior and the parameter semantics. However, given the absence of annotations and the existence of sibling tools, a brief note on when to prefer this over list_reports would have made it fully complete, but overall it is sufficient for a simple list operation.

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 schema has zero description coverage, but the description explicitly states 'optionally scoped to a workspace (group) ID', which explains the purpose of the workspace_id parameter. This compensates for the lack of schema descriptions, though it does not specify format or constraints.

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 the tool's action ('List datasets') and its resource (datasets), distinguishing it from sibling tools like list_workspaces, list_reports, and list_dashboards. The optional workspace scoping is a specific qualifier that further clarifies the purpose.

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 on when to use the tool (to list datasets, optionally scoped by workspace ID). It does not explicitly mention alternatives or when not to use, but the sibling list makes the differentiation clear, and the optional scope gives a targeted use case.

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