isw_unblock_prepaid_card

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

With no annotations, the description carries the burden of behavioral disclosure. It only states the action and a parameter requirement, omitting details like idempotency, side effects, authorization needs, or error states. This is insufficient.

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 extremely concise (two sentences), which is good for conciseness. However, it lacks necessary detail, making it under-specified rather than efficiently informative.

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, no output schema, and similar sibling tools, the description is critically incomplete. It does not explain the function of extra, amountKobo, amountNaira, or requestRef, nor what the tool returns or fails on.

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?

The description adds no meaning beyond the input schema. The confirm requirement is already described in the schema. Other parameters like cardPan, extra, amountKobo, and requestRef are left unexplained. Schema coverage is 50%, but the description does not compensate.

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 prepaid card,' specifying the verb and resource. However, it does not differentiate from the sibling tool 'isw_unblock_card,' which likely applies to non-prepaid cards.

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 required parameter condition. But it offers no guidance on when to use this tool versus alternatives like 'isw_unblock_card' or 'isw_block_prepaid_card,' nor any prerequisites or context.

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