auth_logout

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

Description details specific behaviors: closes browser sessions, deletes cookies/Chrome profile, preserves notebook data. Adds context beyond annotations (destructiveHint, idempotentHint) by explaining what is destroyed and what is kept.

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?

Well-structured with bullet points, numbered steps, and clear sections. Slightly wordy but all information is relevant and front-loaded.

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?

For a zero-parameter tool with an output schema, the description fully covers behavior, side effects, and post-conditions. No gaps.

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 baseline 4 is appropriate. The description clarifies the tool's operation without needing parameter details.

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 'De-authenticate (logout)' and lists specific use cases (security, shutdown, clearing auth). It distinguishes from siblings like auth_setup and auth_switch by focusing on logout.

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?

Explicitly provides when to use (security, shutdown, clearing auth) and what it does not do (preserve notebook data). Also gives guidance on next steps: re-authentication via setup_auth or re_auth, and verification with get_health.

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