create_auth_logout

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

Annotations already indicate non-read-only, non-destructive, and idempotent behavior. The description adds the specific side effect of clearing the session cookie, which provides additional context beyond the annotations. However, it does not discuss prerequisites like requiring an active session or potential consequences, so it is adequate but not rich.

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 short sentences with no filler. It front-loads the primary action and includes the HTTP endpoint, making it extremely efficient and easy to parse.

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 simple no-parameter logout operation, the description is largely complete. It states the action and the side effect, and the output schema exists to document the response. Minor missing details like authentication requirements are implied and not critical for a logout tool.

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, and the schema coverage is 100% (vacuously). The description adds no parameter-specific details because none exist, and the baseline for zero-parameter tools is 4, as the schema already fully documents the absence of inputs.

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 action ('Sign out') and the specific resource ('session cookie'), with a distinct verb and resource that distinguishes it from sibling auth tools like create_auth_local and create_auth_plex. It is unambiguous and self-explanatory.

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 implies when to use this tool (when the user wants to log out) through its name and action, but it does not explicitly mention alternatives or conditions for choosing this over other auth-related tools. No exclusions are stated, but the purpose is obvious.

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