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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered, and the description usefully discloses that the tool is bidirectional (block or unblock). It does not say which parameter flips the direction, whether existing messages are affected, whether the change is reversible, or what permissions are required — meaningful gaps for a state-changing moderation tool.

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 short sentence, front-loaded with the verb and resource, with no filler. The '(M-02)' spec reference is opaque to an agent but costs almost nothing.

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?

An output schema exists, so return values need not be described, but for a three-parameter mutation tool with zero schema coverage the description is too thin: it omits the toggle parameter's default, permission requirements, and any effect on existing conversation content. An agent could plausibly call it with the wrong intent on the 'blocked' flag.

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%, so the description carries the full burden for three parameters. It never names conv_key, member_ref, or blocked, and crucially never explains that 'blocked' defaults to true and controls the block/unblock direction — the single most error-prone parameter here. Only the self-describing parameter names compensate.

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 (block/unblock) and resource (member in a conversation), so the agent knows exactly what operation is performed. It does not distinguish itself from the nearby sibling mute_conversation, which is a closely related moderation action, so it stops short of a 5.

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?

There is no guidance on when to block versus mute_conversation, who is permitted to block, or what preconditions must hold. The only hint is the parenthetical '(or unblock)', which implies a toggle but never states how to select the direction.

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