repayment

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

Annotations already set readOnlyHint=false, indicating a write operation, so the description doesn't need to restate that. It does add behavioral context by enumerating two possible actions (submit and list), which shapes expectations. However, it does not disclose details like confirmation requirements or dry-run behavior beyond what the schema provides.

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 a single sentence, very concise and front-loaded with the core purpose. However, the literal '[VERB]' prefix is an artifact that should have been replaced, and the structure could be slightly cleaner without it.

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?

The tool has 9 parameters and no output schema, yet the description is minimal. It does not explain return values, how the two modes differ in response, or how parameters like confirm, dryRun, and lists interact. Given the complexity, the description is insufficient for an agent to fully understand the tool's behavior.

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?

All 9 parameters have descriptions in the schema (coverage 100%), so the baseline is 3. The description itself adds little parameter-level meaning, but it does reinforce the split between 'submit' and 'repayable' actions, which aligns with the action parameter enum.

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 states a specific verb ('repay') and resource ('account liabilities'), and clearly distinguishes between two modes: submitting a repayment or listing repayable coins/amounts. This differentiates it from sibling tools like deposit or withdraw, which handle funding or withdrawals.

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 implies when to use the tool—when you need to repay liabilities—but does not explicitly mention alternatives or exclusions. The two modes ('submit' vs 'repayable') give hints on sub-usage, but there is no direct comparison to sibling tools.

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