unblock_contact

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

No annotations are provided, so the description bears full responsibility. It discloses one behavioral trait: 'The contact is NOT notified that they were unblocked.' However, it misses other potentially useful details like whether messages sent during the block are delivered or if there are any permissions required. The disclosure is good but incomplete.

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?

The description is two sentences plus a short usage guideline sentence. It is front-loaded with the main action and contains zero wasted words. Highly efficient.

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 tool with one parameter (fully described), no output schema, and no nested objects, the description covers all relevant aspects: action, effect, notification behavior, and sibling references. It is fully complete for the tool's complexity.

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%, and the description adds no additional semantics beyond the schema's parameter description ('Phone number to unblock (E.164 format)'). Baseline 3 is appropriate as the schema already provides sufficient detail.

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 clearly states the verb 'Unblock', the resource 'Signal contact', and the effect 'restoring their ability to send you messages and calls'. It distinguishes from siblings like 'block_contact' and 'list_contacts'.

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 description explicitly provides when to use this tool ('Unblock a previously blocked Signal contact') and alternatives ('Use block_contact to re-block, or list_contacts to see which contacts are blocked'). This offers clear context for selection.

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