reddit_auth_logout

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

Beyond the annotations (destructiveHint=true, idempotentHint=true, readOnlyHint=false), the description discloses additional behavioral details: forgetting the token is destructive and irreversible from the tool's perspective, it does not revoke the app server-side, and it distinguishes between anonymous and account-scoped functionality. This provides agent-facing transparency that annotations alone do not convey.

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?

Three sentences, each carrying clear value. The core action is front-loaded in the first sentence, followed by behavioral effects and a critical limitation with a redirect URL. No filler, redundancies, or restating of the tool name.

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, no-output-schema tool, the description covers all essential context: what it does, what happens afterward, what it does not do, and where to go for the complementary action. The annotations already cover idempotency and destructiveness, so nothing an agent needs to call it correctly is missing.

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 the input schema is trivial. The description adds meaning by explaining what entity is affected (the stored refresh token) and the scope of the action. With no parameters, the baseline is 4, and the description adequately clarifies the operation without needing to document parameter semantics.

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 opens with a specific verb and resource: 'Forget the stored Reddit refresh token.' This clearly identifies the logout action and differentiates it from siblings like reddit_auth_login and reddit_auth_status. It also specifies the operational consequence ('account-scoped tools stop'), leaving no ambiguity about what the tool does.

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 clearly implies the tool is used to log out by forgetting the stored token. It provides context on effects (anonymous browsing remains, account-scoped tools stop) and an important exclusion: it does not revoke the app on Reddit's side, with an explicit pointer to the revocation URL. However, it does not explicitly name alternative sibling tools or state 'use this when you want to log out,' relying on the tool name and context.

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