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

With no annotations, the description carries the full behavioral burden. It does disclose the key trait an agent needs — who is permitted to call it (board moderators vs. unrestricted admins) — which is real value beyond the schema. It does not say what happens if the post is not currently pinned, nor whether the operation is idempotent or how it can be reversed.

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?

A single front-loaded sentence with no filler; the action and its authorization qualifier are both immediately visible.

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 mutation with no annotations and no output schema, the description covers purpose and permissions, which is roughly the minimum viable set. It still leaves the postId parameter and error/no-op behavior unexplained, so it is adequate but not complete.

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 coverage is only 50%: boardSlug is documented ('Board slug from list_boards') but postId has no description beyond format:uuid, and the tool description adds nothing about either parameter. At half coverage the description should compensate for the undocumented postId, and it does not.

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 precise verb+resource pair ('Remove the pin from a board post') that is unambiguously the inverse of sibling mod_pin_post and distinct from admin_set_pin/admin_delete_pin. An agent can select it on the verb alone without opening the 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?

The parenthetical gives the authorization precondition ('any moderator of that board; admins unrestricted'), which is useful context for deciding whether the caller may use it. But it never states when to prefer this over adjacent tools such as admin_delete_pin or admin_set_pin, so alternative-routing guidance is absent.

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