openemis_logout

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

No annotations provided, so description carries full burden. It discloses that JWT is kept in local database, it's session-level only, and transport-specific behavior (HTTP vs stdio). Fully transparent about what happens and what persists.

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 unnecessary words, front-loaded with main action. Could be slightly more concise on JWT and transport details, but overall efficient and clear.

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?

No output schema or annotations, but description fully explains behavior: what it does, side effects on future calls, persistence of JWT, transport handling. Complete for a simple 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?

Zero parameters, schema coverage 100%. Description adds no parameter info because none exist. Baseline score of 4 for zero-param tools is appropriate; the description focuses on behavior rather than parameters.

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 tool clears the current per-user session and explains the effect on subsequent calls (revert to default credentials). It distinguishes from related tools like login and whoami by specifying the session-level scope.

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 explains when to use (to log out user) and the post-condition (default credentials, JWT retained). No explicit when-not, but context with siblings implies not needed for permanent invalidation. Clear and actionable.

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