skydemon_logout

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that only the in-memory session is dropped and SkyDemon's own files are untouched, which is important side-effect context. However, it omits postconditions such as whether subsequent API calls will fail until login and whether logout is idempotent or requires an existing session.

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 front-loaded sentence with no wasted words. The core action is stated first, and the scope clarification is provided compactly in parentheses.

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 zero-parameter logout tool with no output schema, the description covers the core effect and explicitly limits the scope to the in-memory session. It stops short of describing the post-condition that later calls may require login, but that is largely inferable from the sibling login 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?

The tool takes zero parameters, so there are no parameter semantics to explain. The schema description coverage is 100% and no parameter information is needed, making the baseline score of 4 appropriate.

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 states a specific verb and resource: "Drop the in-memory session." It also scopes what is not affected by noting it "does not touch SkyDemon's own files." It does not explicitly differentiate from siblings, though logout vs. login or session_status is clear from the tool name.

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?

There is no explicit when-to-use guidance, no prerequisites, and no alternatives named. The action is implied by the name, but the description does not say when a caller should log out or what to do if no session exists.

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