ariel_auth_logout

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

The description aligns with the annotations (readOnlyHint=false, destructiveHint=true) and adds specific value by naming the destructive effect: 'clear stored session'. It clarifies that the operation mutates local session state, though it does not detail whether a server-side token is revoked.

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?

A single sentence conveys the action, the target, and the side effect without wasted words. The phrasing is front-loaded and easy to parse.

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 zero-parameter logout tool, the description plus annotations provides all necessary context: it is destructive, read-write, and affects the stored Bluesky session. No return value documentation is required because there is no output schema and the operation's result is straightforward.

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 is empty, so there are no parameters to document; the baseline of 4 applies. The description adds no parameter details, but none 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 names a specific action ('Log out') and the target resource ('Bluesky'), and adds the concrete side effect 'clear stored session'. It is immediately distinguishable from sibling ariel_auth_status, which checks session state rather than ending it.

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 intended context—when an agent needs to end the current Bluesky session—is clear from the description. There are no explicit alternative comparisons or when-not-to-use clauses, but with no parameters and a unique purpose among the auth siblings there is little ambiguity.

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