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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states the immediate effect ('Takes effect immediately') and the consequence ('the next call using that token fails'). This is non-obvious and valuable, though it doesn't mention reversibility or other side effects.

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 two short sentences, front-loaded with the action and resource, and includes a useful cross-reference. Every word earns its place with 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 simple revoke operation with a single required parameter and no output schema, the description sufficiently covers purpose, how to use it, and what to expect. The reference to list_tokens rounds out the workflow context.

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 only provides the parameter name and type, with no description. The description adds meaning by clarifying that token_id refers to a Personal Access Token and directs the user to brainkb_list_tokens to find the ID. This compensates well for the 0% schema description coverage.

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 ('Revoke') on a specific resource ('Personal Access Tokens') and identifies the selection mechanism ('by id'). It also references brainkb_list_tokens, which distinguishes it from other token-related operations like create_token or use_token.

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?

It tells you to use brainkb_list_tokens to obtain the token ID, and it clarifies the immediate effect. This gives clear context for when to use the tool, though it doesn't explicitly list any exclusions or alternative tools beyond the listing tool.

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