pbi_list_workspaces

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

The description discloses return format and filter behavior, but lacks annotations, so it must cover more. Authentication requirements and side effects (none) are implied but not explicit.

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 with clean 'Args' and 'Returns' sections, front-loaded purpose, and no superfluous text.

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 one simple parameter and output schema, the description covers the core functionality and return format well. Minor gap: no mention of dependency on pbi_auth (though implied).

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 single parameter 'filter' is fully explained in the description as 'case-insensitive substring match,' adding meaning beyond the minimal schema (no description, default only).

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 Power BI workspaces accessible to the authenticated user,' specifying a verb and resource, and distinguishes it from sibling tools like pbi_list_datasets.

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?

Usage is implied as the default for listing workspaces, but no explicit when-to-use or alternatives are mentioned. Exclusions or prerequisites (e.g., authentication) are absent.

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