panelica_sessions_post_v1_sessions_revoke_all

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

Annotations already carry readOnlyHint=false and idempotentHint=false; the description adds a required scope ('accounts:write') and confirms 'Mutating: changes server state', which is consistent with the annotations. It does not disclose the most operationally relevant behavior — that revoking ALL sessions likely invalidates the caller's own current session — nor any side effects. No annotation contraidiction.

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?

Five short labeled lines with the action front-loaded; each line carries one fact (action, HTTP method, category, scope, mutation). The HTTP POST line mildly duplicates the tool name's 'post_v1_sessions_revoke_all', but it is cheap and aids routing.

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?

Adequate for a no-required-param mutating action: it gives the endpoint, category, required scope, and mutation flag. Gaps include no warning about the caller's own session being affected, no body expectations, and no indication of the response (and since no output schema exists, the description is the only place that could be covered).

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?

Schema description coverage is 100%, so the description need not compensate per the baseline. However, the sole param's description is a stub ('Schema not statically declared — see API docs'), so the agent learns nothing about what the body should contain; the tool description adds no parameter info either.

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 opening line 'Revoke all sessions' states a specific verb and resource, and the scope word 'all' distinguishes it from the key siblings panelica_sessions_get_v1_sessions (list sessions) and panelica_sessions_delete_v1_sessions_id (revoke a single session). However, the description never names those siblings explicitly, so differentiation is implied rather than stated.

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?

There is no guidance on when to use this tool versus its alternatives. It never mentions that a single session can be revoked with panelica_sessions_delete_v1_sessions_id or that listing sessions uses panelica_sessions_get_v1_sessions, so an agent choosing between scoped and bulk revoke gets no decision support beyond the word 'all'.

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