stremio_logout

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that the credential is local ('stored ... on this machine'), implying this is a local-state mutation rather than a server-side token revocation, but it does not say whether other machines/sessions are affected, whether re-login is required afterward, or that the action is irreversible without credentials.

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 short sentence with the action front-loaded and zero filler. Nothing to trim and nothing buried.

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 tool with an output schema already documenting return values, the description covers what the agent needs to select and invoke it. The only shortfall is the unstated post-condition (does the agent/user need to re-authenticate afterwards).

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 is no parameter semantics to explain; per the rubric this yields a baseline of 4. The description correctly implies a no-argument operation.

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?

States a concrete verb ('forget') and resource ('the stored Stremio auth key'), and adds a scope qualifier ('on this machine') that distinguishes it from a server-side sign-out. It is clearly the inverse of the sibling stremio_login, though it never names that sibling explicitly.

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?

Usage is implied — the agent can infer this is the tool to call when it wants to drop stored credentials — but there is no explicit when-to-use, no prereq/state guidance, and no mention of stremio_login as the counterpart/alternative. Adequate but with clear gaps.

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