blocklist

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

Annotations already declare destructiveHint=false, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds no behavioral context beyond restating the operations: it says nothing about idempotency, reversibility, permissions, or what happens to an unblocked/blocked contact.

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 listing behavior is stated first. It is efficient, though the compactness contributes to the missing detail noted elsewhere.

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. However, for a multi-action tool with an under-documented schema, the description should explain the action values and the account parameter; it only hints at the operations, leaving the agent to infer parameter semantics.

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 33%: the 'contact' parameter is documented as required for block/unblock, but 'action' and 'account' have no explanation. The description partially compensates by enumerating the three behaviors that correspond to the action enum, but it never names the enum values or explains 'account'.

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 names the resource (contacts bloqués) and the three concrete operations (list, block, unblock), giving a clear verb+resource scope. It does not, however, explicitly distinguish itself from related siblings like get_contact or search_contacts, 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 use this tool versus alternatives, nor any prerequisites or exclusions. The only usable signal is the implicit list of operations, which the agent must map onto the 'action' enum on its own.

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