auth_logout

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

Annotations already indicate destructiveHint=true, so the description adds value by specifying that it clears cached credentials and does not revoke environment-set API keys. This nuanced behavior beyond the annotation is useful.

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 sentences, no wasted words. Front-loaded with the core action, then immediate clarification. Ideal conciseness.

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?

While the description explains what it does and does not do, it omits the return value or outcome (e.g., success message or error behavior). With no output schema, the agent might need that info. Acceptable but incomplete.

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 input schema has no parameters (0 params), so schema_description_coverage is 100%. With baseline 4, the description correctly offers no parameter info since none exist.

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 'Disconnect this MCP server from your OpenEphemeris account by clearing cached credentials.' It uses a specific verb-resource pair and distinguishes it from sibling tools like auth_login and auth_status by focusing on disconnection.

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 tells when to use the tool and explicitly states what it does NOT do ('Does NOT revoke the API key... only clears device-auth cached credentials'), which helps the agent avoid misuse. It lacks explicit when-not-to-use scenarios but provides clear context.

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