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

Annotations already disclose that this is a non-readonly, non-destructive mutation. The description adds the outcome ('so they can post new content again'), but omits auth requirements, webhook/audit side effects, and why idempotency is false. Given annotations cover the safety profile, this is adequate but thin.

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 and immediately followed by the effect. No wasted words; the first line duplicates the title but serves as a clear lead-in.

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 mutation with one nested request parameter, the description covers the core outcome but omits permission/project-context nuances (projectId requirement with org keys) and the audit/webhook role of the reason field. These are present in the schema, but the description does not tie them together for the agent.

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 reported as 0% for the top-level request object, and the description adds no parameter meaning at all. It does not mention the required author id, optional reason, or project scoping, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Unblock author') and explains it applies to a 'blocked or suspended author'. This clearly distinguishes it from the sibling authors-block and authors-suspend tools, which perform the inverse operation.

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 condition for use is explicit: unblock a blocked or suspended author so they can post again. However, it does not name alternatives (e.g., authors-block, authors-suspend) or state when not to use it, leaving routing to inference.

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