Sign out

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

The description discloses what gets destroyed (cached Microsoft account and local token cache) and the post-condition (user must re-authenticate). This goes beyond the annotations (destructiveHint=true, idempotentHint=true) by specifying the exact side effects and consequences, adding valuable behavioral context.

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 two sentences, front-loaded with the primary action, and every word earns its place. It is efficient and to the point.

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 simplicity (no parameters, no output schema), the description fully explains the tool's purpose, its effect on the system, and the required follow-up. Combined with the annotations, nothing essential is missing.

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 tool has zero parameters, so there are no parameter semantics to explain. Per the baseline for 0-parameter tools, the description is adequate without needing to detail any arguments.

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 the tool's action: 'Remove the cached Microsoft account and delete the local token cache file.' This is a specific verb-resource pair that unambiguously distinguishes signOut from sibling tools like authenticate, authStatus, and getOutline.

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 gives clear context by specifying what the tool does and the consequence ('The user must authenticate again afterwards'), making it obvious when to use it. It does not explicitly mention alternatives or exclusions, but the context is sufficient for correct selection among the listed siblings.

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