pbi_list_datasets

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

Since no annotations are provided, the description bears full responsibility. It correctly indicates a read operation by using the verb 'list,' and describes the return format. However, it does not disclose potential errors, permissions required, or any side effects, which is acceptable for a simple list but could be more thorough.

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 plus a usage note, front-loaded with the main purpose. It efficiently conveys the tool's function without unnecessary detail, though a slightly more structured format (e.g., bullet points) could improve scannability.

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?

Given the tool's simplicity (one parameter, list operation), the description is mostly complete, specifying the parameter and return fields. It lacks guidance on where to obtain the workspace_id and error handling, but the presence of an output schema (per context) covers return format details.

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?

With only one parameter and 0% schema description coverage, the description adds minimal value: 'workspace_id: The workspace (group) ID.' This clarifies the parameter's purpose but does not elaborate beyond the name, such as format or source.

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 'List datasets in a Power BI workspace,' specifying the action (list), resource (datasets), and context (workspace). This distinguishes it from sibling tools like pbi_dataset_info (single dataset details) and pbi_list_workspaces (list workspaces).

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 implies usage requires a workspace_id and hints at the return, but it does not explicitly state when to use this tool over alternatives. No mention of prerequisites like obtaining workspace IDs from pbi_list_workspaces or when not to use it.

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