bsky_logout

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

No annotations are provided, so the description carries full burden. It states the tool destroys a login session, implying a mutation with side effects, but lacks details on permissions needed, whether it's reversible, rate limits, or what happens to other sessions. This is a significant gap for a destructive operation with zero annotation coverage.

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, efficient sentence in Japanese that directly states the tool's function without redundancy. It's appropriately sized and front-loaded, with no wasted words.

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?

Given the tool's complexity (destructive operation), lack of annotations, and presence of an output schema (which may cover return values), the description is minimally adequate but incomplete. It covers the basic action but misses critical behavioral details like authentication requirements or error conditions, leaving gaps for safe agent use.

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 description specifies that the 'handle' parameter identifies the session to destroy, adding meaning beyond the schema's minimal coverage (0%). With only one parameter, the description effectively clarifies its purpose, though it doesn't detail format constraints (e.g., handle syntax).

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 action ('destroy login session' / logout) and the target resource ('specified handle'), which is specific and unambiguous. It distinguishes from siblings like bsky_login (login) and bsky_refresh_session (refresh), but doesn't explicitly contrast with other session-related tools.

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites (e.g., must be logged in first), or consequences. It doesn't mention sibling tools like bsky_login for re-authentication or bsky_refresh_session for session renewal, leaving usage context implied rather than explicit.

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