unblock_user

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

The description adds no behavioral context beyond what annotations already declare. Annotations indicate a write operation (readOnlyHint=false) and non-destructive, but the description does not explain effects, permissions, or error conditions. It does not contradict annotations, but it provides zero added transparency.

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 a single short phrase, which is under-specification rather than genuine conciseness. It lacks essential details and does not earn its place by adding value beyond the tool name.

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?

The tool has two parameters and no parameter descriptions, yet the description provides no context about what the user should be, preconditions (e.g., user must be blocked), or the role of 'my_stories_from'. Despite having an output schema, the description is severely incomplete for an agent to use it reliably.

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 does not explain any parameters. The 'user' param could be an ID or username, and 'my_stories_from' is entirely cryptic. The description fails to compensate for the lack of parameter documentation, leaving the agent unable to correctly populate inputs.

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 'Unblock user' clearly states the action and target resource, and it is distinct from sibling tools like block_user by being the inverse operation. It is a specific verb+resource that leaves no ambiguity about the tool's core function.

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 description provides no guidance on when to use this tool versus alternatives, such as when a user has been previously blocked or when to use unban_participant. It gives no context about prerequisites or exclusions, so the agent lacks usage direction beyond the name.

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