Clear local Zé token

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

The exact file that will be destroyed is named, adding concrete behavioral detail beyond the destructiveHint annotation. It also mentions the intent gate; this is already in the schema, but the file path is genuinely useful 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?

Two short sentences, front-loaded with the destructive action and the one critical condition. 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 logout tool, the essential call information is present: exact file path, intent precondition, and destructive role. It doesn't describe the response format or post-logout state, but that is a minor gap given the tool's low complexity and no output schema.

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?

Schema description coverage is 50%: explicit_user_intent has a schema description and the tool description merely restates it, while response_format has no description but its enum and default offer adequate meaning. The description adds little paramnformation beyond the schema.

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?

States the exact action — 'Deletes ~/.ze-mcp/tokens.json' — with a specific verb and resource, and the title confirms clearing the local Zé token. This clearly distinguishes it from sibling tools like ze_connection_status and ze_cancel_order.

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 makes the key precondition explicit: only use when the user has explicitly asked, matching the explicit_user_intent parameter. It doesn't name alternatives or when-not-to-use scenarios, but the tool's logout role is self-evident next to the unrelated siblings.

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