unblock_card

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

Despite no annotations, description discloses side effect (clearing blocked flag) and return value (resolved blocker object). Doesn't cover error states or permissions, but adequate.

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?

Five sentences covering purpose, side effect, prerequisite, and parameters. First sentence is clear. No redundant text.

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?

Covers main behavior, return type, and side effect. Lacks details on error handling or idempotency, but for a simple unlock operation it's sufficient.

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?

With 0% schema coverage, description adds crucial context: example for card_ref, origin for blocker_id, optional nature of resolution. Helps agent understand usage beyond types.

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 action ('Resolve (unblock)') and the resource ('specific blocker on a card'). It distinguishes from sibling tools like 'block_card' by focusing on unblocking.

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?

Provides guidance on when to use ('If this was the last active blocker...') and prerequisite step ('Use list_blockers() to find the blocker_id'). Lacks explicit when-not-to-use but sufficient.

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