Log out of Redbooth

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

The description states the tool removes locally stored OAuth tokens, i.e. it modifies environment state, while the annotations declare readOnlyHint=true (destructiveHint=false). This is a direct conflict on the read-only/mutation axis. Per the rubric, a contradiction with annotations caps this dimension at 1.

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?

One sentence that front-loads the account disconnect and follows with the token removal. No filler, no redundancy.

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 zero-parameter, no-output-schema tool the description covers the essential behavior: ending the session and clearing credentials. It does not say whether the disconnect is server-side revocation or purely local, or what happens if no session exists, but the complexity is low enough that this is a minor omission.

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 schema has zero parameters, so the baseline is 4. The description adds no parameter behavior because there is nothing to parameterize, which is acceptable here.

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?

Names a specific verb+resource pair ('Disconnect the current Redbooth account') plus the concrete side effect ('remove locally stored OAuth tokens'). An agent can distinguish this from the sibling 'login' without opening either schema.

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 only implied: 'disconnect the current account' suggests the agent invokes it when ending a session, but there is no explicit when/when-not statement or named alternative. For a tool whose only counterpart is 'login', this is adequate but leaves the trigger condition to inference.

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