End the Session

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety bar is partly covered. The description still adds real value by disclosing exactly what is destroyed (the WalletConnect pairing and the local session) and the post-condition that re-authentication will be required before signing, which the annotations cannot express.

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, front-loaded with the action, followed by the consequence. Every clause carries information the agent needs and there is no filler.

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 mutation with annotations already covering the safety profile, the definition covers effect, scope, and aftermath adequately. Minor gaps remain, such as whether ending the pairing requires network interaction or can fail, but nothing essential for calling 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 no parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies for a zero-parameter schema.

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 states a specific action and its two concrete effects: ending the WalletConnect pairing and clearing the local session. This is far more precise than the bare name 'logout', though it does not explicitly name the contrasting sibling (connect_wallet) the way a top-tier definition would.

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?

Usage is implied by the verb and the stated consequence ('the user will need to authenticate again before signing anything'), which gives the agent enough context to know the cost of calling it. There is no explicit when-to-use or when-not-to-use guidance versus siblings such as connect_wallet or get_auth_status.

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