authenticate

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

With no annotations provided, the description carries the full burden and delivers excellent behavioral context. It discloses the OAuth 2.0 device code flow mechanics, the two-step interaction pattern (browser URL + code), local credential caching behavior, and the ~90 day refresh token expiration timeline.

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 well-structured with clear paragraph breaks separating purpose, usage conditions, flow mechanics, and caching details. Every sentence provides necessary information without redundancy, making it appropriately concise yet complete.

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 that this is an authentication tool with an output schema (implying structured return data), the description appropriately focuses on the conceptual flow and when to invoke rather than specific return field syntax. It adequately covers the authentication lifecycle and prerequisites for the sibling Power BI tools.

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 input schema contains zero parameters, which establishes a baseline score of 4. The description correctly requires no additional parameter clarification since there are no inputs to document.

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 explicitly states the tool 'Authenticate[s] with Power BI using the OAuth 2.0 device code flow,' providing a specific verb, resource, and authentication method. It clearly distinguishes this from the sibling 'logout' tool by describing the login flow and credential caching.

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 explicit guidance: 'Call this tool first if you have never logged in, or if a previous call returned "Not authenticated".' It also details the two-step invocation pattern (first call for URL/code, second call to complete), which is essential for correct sequencing.

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