Block or Unblock User Account

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds substantial context beyond them: blocking severs existing friendships and pending requests and prevents future contact or profile discovery. The identity prerequisite is also useful context. It stops short of describing failure modes or whether unblocking restores prior connections, which a destructive tool could state.

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 sentences, front-loaded with the primary action and its consequences, then the alternative routing. No redundant restatement of the title or the schema.

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?

Output schema exists, so return values need no explanation; annotations cover safety and idempotency; the description covers consequences, prerequisites, and the sibling alternative. Nothing an agent needs to invoke this correctly is missing.

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 100%, so both accountId and the action enum are documented in the schema itself. The description adds only that the operation applies to an accountId and that block is the meaningful default path, not new meaning about formats or constraints. Baseline 3 is correct.

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 ('Block an accountId ... or unblock a previously blocked accountId') and immediately distinguishes the two modes. It also names the sibling tool it is not, so an agent can separate it from socialwtf_remove_connection without opening either 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?

Explicitly routes the agent: 'Prefer socialwtf_remove_connection if you only want to unfriend without blocking future connection requests.' It also states a prerequisite ('Requires a registered local identity'), covering both the when-to-use and precondition dimensions.

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