Cerrar sesión

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

The description only states the basic action of invalidating a token. With no annotations, it lacks details on side effects (e.g., whether other sessions are affected), authentication requirements, or error conditions. Minimal disclosure beyond the core effect.

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 very short (one sentence) and front-loaded with the verb. It is concise but could be slightly expanded without losing efficiency. 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?

For a simple one-parameter tool with no output schema, the description is mostly adequate. It explains the action and parameter origin. However, it could mention the result (e.g., 'subsequent requests with this token will fail') to be fully complete.

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 coverage is 100% for the single parameter. The description adds value by linking the token to the 'login' tool ("obtenido en 'login'"), clarifying the token's origin, which goes beyond what the schema provides.

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 of invalidating an active session token ("Invalida un token de sesión activo"), which is specific and distinct from sibling tools like 'login' or 'whoami'. However, it could be more explicit about the overall effect (e.g., logging out the user).

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. While it logically follows 'login', the description does not state prerequisites or context (e.g., 'Call after user requests logout').

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