Log out of Wilma

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

Goes well beyond the annotations by disclosing the hidden mechanics: one session per account, login credentials persist, and the next Wilma tool call silently re-authenticates and kicks the user's browser session. That second-order side effect is not derivable from readOnlyHint=false / destructiveHint=false / idempotentHint=true, so the description carries real load here.

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?

Three sentences, front-loaded with purpose, then the reason, then the ordering hazard. Every clause carries decision-relevant information: session uniqueness, credential persistence, and the follow-on-call trap.

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?

With no parameters and no output schema, the only thing an agent could get wrong is sequencing and re-login behavior, and both are covered explicitly. Nothing needed to invoke this 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 no parameters, so there is nothing for the description to disambiguate; per the zero-parameter baseline this is a 4. It adds no spurious argument talk, which is correct.

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 and resource ("End WilmAI's Wilma session") and anchors it to a familiar analogue ("as Wilma's own Log out does"), which immediately distinguishes it from wilma_login and every other read-oriented sibling.

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?

Gives explicit trigger conditions ("when the user wants to use Wilma in their browser or asks to log out") and an explicit exclusion ("don't call other Wilma tools afterwards unless the user asks"). This is exactly the when/when-not structure an agent needs for a terminal action.

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