isw_unblock_card

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

With no annotations, the description must fully disclose behavior. It only states 'Unblock a card' and a confirm requirement, omitting details like side effects, response, rate limits, or whether the action is reversible. Minimal disclosure.

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 very short (one sentence + note), which is concise, but fails to include essential information. It is front-loaded but at the expense of completeness.

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?

Given 6 parameters (including an object), no output schema, and no annotations, the description is severely inadequate. It does not explain the role of 'extra', amounts, or requestRef, nor what the tool returns. Critical gaps persist.

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 50% (3 of 6 parameters have descriptions). The description only emphasizes the confirm parameter, adding no meaning to cardPan, extra, requestRef, amountKobo, or amountNaira. These fields remain unclear.

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 'Unblock a card', specifying the action and resource. However, it does not distinguish from the sibling tool 'isw_unblock_prepaid_card', which could cause confusion.

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 mentions 'Requires confirm: true', providing a requirement for invocation. But it lacks guidance on when to unblock, prerequisites (e.g., card must be blocked), or when to use alternatives like 'isw_block_card'.

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