isw_block_prepaid_card

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

With no annotations, the description is the sole source of behavioral disclosure. It only states that blocking requires 'confirm: true', but does not explain consequences (e.g., card usage disabled, reversibility, or side effects). This is insufficient for an agent to understand the tool's impact.

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 at two sentences, with no redundant information. It effectively front-loads the core action and the critical requirement ('confirm: true').

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 the tool has 6 parameters, nested objects, no output schema, and multiple similar siblings, the description fails to provide necessary context. It does not explain the role of amounts, the 'extra' object, or what the agent should expect as a response.

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 50%, meaning half of the 6 parameters lack descriptions. The description adds no information beyond what's in the schema, failing to clarify non-obvious parameters like 'extra', 'requestRef', or why 'amountKobo'/'amountNaira' are relevant for blocking a card.

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 'Block' and the specific resource 'prepaid card'. It effectively distinguishes from sibling tools like 'isw_block_card' (for regular cards) and 'isw_unblock_prepaid_card', making the purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives such as 'isw_block_card' or 'isw_unblock_prepaid_card'. The only usage hint is the requirement for 'confirm: true', but this is a technical prerequisite rather than contextual guidance.

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