blackboard_logout

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine value beyond that by scoping the destruction precisely: session plus private profile are removed, while downloaded materials are preserved. It does not mention auth-state side effects or whether re-login is needed.

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?

Two short sentences with no filler; the primary effect is front-loaded and the exclusion follows immediately. Every clause carries information.

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 parameterless logout with no output schema and annotations that already cover safety and idempotency, the description supplies the one thing structured data cannot: the exact blast radius and what is deliberately left untouched. Nothing needed 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 baseline is 4 and there is nothing for the description to clarify on this dimension.

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 specific verb ('Elimina') and the exact resources affected (la sesión y el perfil privados de este MCP), which is unambiguous and distinct from the many read-oriented siblings. It also explicitly rules out the adjacent operation of deleting downloaded materials, preventing confusion with the download_* tools.

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 tool's purpose implies its usage (ending a session), and the counterpart blackboard_login exists in the sibling list, but the description never states when to log out, whether it is required, or what happens to subsequent calls. Usage is only inferable.

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