powerbi_list_workspaces

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

Describes the return format (IDs and names) and common errors, implying a read-only listing. Without annotations, it carries the burden well, though no side-effect disclosure is needed for a list operation.

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?

Two short paragraphs with clear front-loading: purpose and return first, errors second. No wasted words.

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?

Adequate for a simple list tool with an output schema. Covers workspace identification and errors, but could mention pagination or rate limits for completeness.

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?

No parameters exist, so schema coverage is 100%. The description adds value by specifying the scope ('the user has access to') and return structure (workspaces with IDs and names).

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?

Clearly states 'List all Power BI workspaces the user has access to' with a specific verb and resource, and differentiates from sibling tools like get_workspace_id and list_datasets_in_workspace.

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?

Provides context that it is useful for identifying accessible workspaces, but lacks explicit guidance on when not to use or alternatives. Includes common error codes for troubleshooting.

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