isw_check_prepaid_balance

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

No annotations provided; description only says 'check' implying read-only, but no details on side effects, authorization, or what happens if card is invalid. Limited behavioral info.

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?

Single sentence is concise but under-specified. Additional information on parameters or usage would improve without sacrificing conciseness.

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 2 parameters, no output schema, no annotations, and many siblings, the description is severely incomplete. Missing parameter explanations, return value hints, and usage context.

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 0%, and description adds no meaning to parameters. Does not explain cardPan (required) or extra (optional object). Agent cannot infer semantics from description.

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?

Description clearly states verb 'Check' and resource 'prepaid card balance'. It distinguishes from sibling tools like isw_check_debit_balance by specifying 'prepaid', but lacks further specificity like 'using card PAN'.

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 on when to use this tool vs alternatives (e.g., isw_check_debit_balance, isw_confirm_prepaid_sufficient). Implied from name but not explicit.

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