isw_create_payment_link

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

With no annotations, the description carries full burden. It discloses that the endpoint receives kobo and requires confirm: true, but does not explain other parameters like expiryDate, payableCode, or any side effects.

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 two sentences, front-loading the purpose, then adding key constraints. Every sentence adds value without redundancy.

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?

Despite concise purpose, it fails to explain most parameters (expiryDate, payableCode, merchantCode, extra) and does not clarify the output or differentiate from similar tools. A 7-parameter tool with no output schema needs more details.

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 43%, so description needs to compensate. It clarifies the exclusive use of amountNaira or amountKobo and reinforces confirm requirement. Other parameters lack additional meaning.

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 tool creates a shareable payment link, using specific verbs and resource. However, it does not differentiate from sibling tools like isw_create_paycode, which may also create shareable items.

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 provides concrete usage guidance: explicitly provide amountNaira or amountKobo, and require confirm: true. It gives context on when to use but does not mention when not to use or suggest alternatives.

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