Unblock a user

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

Annotations already provide idempotentHint and openWorldHint, reducing the burden on the description. The description adds the context that a previous block must exist, which is useful behavioral scope. However, it does not disclose side effects, errors, or accountId behavior, so it only partially enriches beyond annotations.

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 concise, front-loaded sentence with no filler. The wording 'Lift a previous block' uses every word meaningfully, covering both the action and its precondition.

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 two-parameter tool with no output schema and no sibling differentiation, the single-sentence description is under-specified. It omits how the unblock operation relates to accountId, what response to expect, and how it contrasts with unban_user. The idempotent annotation helps but doesn't fill the missing operational 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?

Schema description coverage is 0%, and the description 'Lift a previous block' only indirectly suggests that the 'user' parameter should be a blocked user. It does not explain 'accountId' or its optional relationship to the operation. Given low coverage, the description fails to compensate and leaves parameter meaning largely to inference from names.

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 'Lift a previous block' clearly identifies the action (removing a block) and resource (a user's block), matching the title. It doesn't explicitly distinguish from sibling 'unban_user' or 'unmute_peer', but the block terminology is distinct enough. Slightly limited by no scope or recipient mention.

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 phrase 'previous block' implies the tool should be used only when a user is currently blocked, providing minimal contextual guidance. However, it offers no explicit when-not-to-use, prerequisites, or alternatives such as 'unban_user' for banned users. This is enough for a simple action but lacks explicit decision support.

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