worksection_logout

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

With no annotations, the description carries the full burden. It discloses the exact effect (delete tokens from disk), the side effect (only local credentials removed), and explicitly states what is not affected (Worksection data). This is transparent and accurate, though it doesn't mention if the operation is reversible or requires authentication state.

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?

Two concise sentences with no fluff. The main action is front-loaded, and the clarifying statement about scope follows immediately. 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 simple, no-argument, no-output tool, the description fully covers what it does and its side effects. It is complete enough for an agent to call it correctly without additional information.

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 no parameters, and schema coverage is 100% (empty schema). The description adds nothing about parameters, but the baseline for zero parameters is 4 because there is nothing to document. It correctly implies no arguments are needed.

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: delete stored OAuth tokens from disk. It specifies the resource (OAuth tokens) and the scope (local credentials), and distinguishes itself from siblings like worksection_login and auth_status by noting that nothing in Worksection itself is affected.

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?

It implies usage: to remove local credentials without affecting remote state. However, it does not explicitly mention when to use it versus alternatives (e.g., logging out entirely) or any prerequisites like being authenticated. The clear scope gives good context, but exclusions are not spelled out.

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