logout

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

With no annotations provided, the description carries the full burden of behavioral disclosure, specifying the destructive side effect of 'clearing the cached credentials' and the consequent requirement to re-authenticate, though it omits details on idempotency or error states when already logged out.

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 consists of two efficiently structured sentences with the core action front-loaded in the first sentence and workflow guidance in the second, containing no redundant or wasted 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 the tool's low complexity (zero parameters), the presence of an output schema (removing the need to describe return values), and the adequate coverage of the authentication state mutation, the description provides sufficient context for invocation.

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, establishing a baseline score of 4; the description appropriately makes no reference to parameters since none exist, requiring no additional semantic clarification beyond the schema.

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 uses specific verbs 'Sign out' and 'clearing' with the resource 'Power BI' and 'cached credentials', clearly distinguishing it from sibling tools like `authenticate` which handles sign-in, while this handles sign-out.

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 workflow guidance by naming the sibling tool `authenticate` as the necessary next step ('call `authenticate` to sign in again'), effectively establishing the tool's place in the authentication lifecycle, though it does not explicitly state negative conditions (when not to use).

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