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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds meaningful caveats: 'The final ZAR amount may differ from the quoted amount', confirmation is required, and a payment_id is returned on success. However, it omits details about irreversibility, failure modes, or permission requirements, so transparency is adequate but incomplete.

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 reasonably concise and front-loaded with the main purpose, followed by workflow context and parameter details. The parameter list is necessary and structured. The phrasing 'any the OTT Mobile supported providers' is awkward but does not significantly harm clarity.

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 that an output schema exists, the description need not explain return values in depth, though it does mention payment_id. It captures the key workflow (step after quote), the quote dependency, the confirmation requirement, and the amount variance caveat. It lacks explicit details about the confirmation mechanism or prerequisites, but is sufficiently complete for a 5-parameter transactional tool.

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 schema has 0% description coverage, but the description fully compensates by documenting all five parameters via @param blocks. It explains that account_fk is a database ID, not an account address, and cannot be 0, and specifies the mobile format as 27XXXXXXXXX. This adds essential meaning beyond the bare schema.

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 'Withdraws ZAR to any the OTT Mobile supported providers' and further specifies it performs the withdrawal based on a quote_id from '/withdraw/to_ott_quote'. This distinguishes it from sibling tools like withdraw_to_ott_quote and withdraw_to_ott_query. Despite minor grammar awkwardness, the verb and resource are specific.

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 explicitly identifies this as 'Step 3' and states it uses the quote_id returned from '/withdraw/to_ott_quote', providing clear workflow context. It also instructs to 'confirm (yes/no) before executing'. It does not explicitly name alternatives or exclusions, but the step-wise context is sufficient guidance.

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