Get Instances Customers Bank Accounts Offramp Wallets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered by structured fields. The description adds nothing beyond that — no note that results are scoped to a single bank account, no ordering, no empty-result or pagination behavior. Not contradictory, but purely redundant.

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?

Three words, front-loaded, zero waste — but the brevity is under-specification rather than economy, since there is no substantive content to be concise about.

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?

A three-required-parameter, three-segment-path retrieval tool with no output schema and only partial schema coverage needs the description to say what is returned and how the IDs relate. The description says none of that, so an agent must infer the entire contract from parameter names.

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 33%: only customer_id carries a description ("Customer ID"), while instance_id and bank_account_id are documented only by name, example, and length constraint. The description compensates for none of this and never explains that bank_account_id scopes the wallet list.

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?

"Get Offramp Wallets" only restates the title and last path segment; it adds no verb-level detail about what is retrieved or in what shape. It does not distinguish itself from the sibling GetInstancesCustomersBankAccountsOfframpWalletsById, which reads identically apart from the singular/plural trailing segment.

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 when-to-use, when-not-to-use, or alternative routing is given. With many near-identical siblings (wallets, blockchain wallets, virtual accounts, bank accounts), an agent has no basis to prefer this tool over those.

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