logout_session

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

With no annotations, the description carries the burden. It discloses that the tool clears authentication state, which is a mutation, but does not mention side effects such as token invalidation, irreversibility, or impact on other sessions. It's 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 a single sentence that is front-loaded with the action and contains no filler. Every word earns its place.

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 one-parameter logout tool with no output schema, the description covers the core action and effect. It lacks details about preconditions (e.g., session must exist) or error behavior, but given the simple nature, it is largely complete.

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 schema already describes sessionId as 'The identifier of the session to log out.' with 100% coverage. The description adds no additional parameter-level meaning, such as format or constraints, so the baseline 3 applies.

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 'Disconnect and log out a WhatsApp session, clearing its authentication state' uses a specific verb (log out) with a specific resource (WhatsApp session) and states the effect (clearing authentication state). It clearly distinguishes from sibling tools like get_session_status or start_session.

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 usage: use when you want to end a session. However, it provides no explicit when-to-use guidance or exclusions versus alternatives like get_session_status or list_sessions. It's clear but implied rather than explicit.

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