transfers.create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention whether transfers are reversible, synchronous/asynchronous, idempotent, or what side effects occur (balance changes, transaction records).

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?

While brief (4 words), this is under-specification rather than effective conciseness. The single sentence merely echoes the tool name without adding actionable information.

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 6 parameters with nested objects, 0% schema coverage, no annotations, and no output schema, the description is grossly inadequate. A financial mutation tool requires explicit behavioral and parameter documentation.

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 the description provides no compensation. It fails to explain what 'source' and 'destination' objects represent, the purpose of 'reason' or 'metadata', or that amount is in smallest currency units.

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 'Create a Ryft transfer' restates the tool name (tautology) and fails to specify what a transfer actually does (e.g., moving funds between accounts). It does not distinguish from sibling tools like transfers.get or transfers.list.

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 provided on when to use this tool versus alternatives like payouts.create, or prerequisites such as account verification requirements. No mention of when transfers might be rejected.

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