riseup_logout

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

No annotations are provided, so the description carries the full burden. "End the session and forget it" does disclose the core behavior — the session is terminated and not persisted — which is useful. However, it says nothing about whether authentication is required first, whether the server-side token is revoked, or what happens if called with no active 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?

One short, front-loaded sentence that puts the action first and the effect second. "here" is mild filler, but nothing else is wasted.

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-param, no-output tool this is close to sufficient, but with no annotations and no output schema the description could reasonably add that no further authenticated calls succeed until riseup_login is called again. It stops just short of fully closing the loop.

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 document; per the baseline for 0 params this is a 4. The description correctly implies no arguments 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?

Specific verb ("Sign out") plus resource ("RiseUp" session), and the effect is stated. It is trivially distinguishable from siblings riseup_login and riseup_session_status, so an agent can route correctly without opening any schema.

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?

"Sign out of RiseUp here" implies the usage context (you have an active session you want to terminate), but there is no explicit when-to-use/when-not statement and no named alternative such as riseup_session_status for checking state. Implied guidance only.

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