loan_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. It mentions the return of loan order details but does not disclose authentication requirements (beyond an optional jwt), rate limits, or side effects. The '[PRIVATE]' tag is noted but not a behavioral trait. Adequate but not exhaustive.

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 sentences, starting with the core purpose, then explaining key parameter usage, then mentioning the output. Every sentence is informative and no wasted words.

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?

For a 7-parameter tool with no output schema, the description provides moderate context. It explains the core logic but lacks details on prerequisites (e.g., need for collateral balance), error handling, or the structure of the returned 'loan order details'. Could be more complete.

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 100%, but the description adds significant value by explaining the logic behind amount_type and how guarantee_amount vs loan_amount are used depending on mode. It also clarifies the user_symbol default and purpose. This goes beyond the schema's descriptions.

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's action ('Create a new loan'), the resource (loan), and the method (cryptocurrency collateral). It distinguishes from sibling tools (e.g., loan_get_orders, loan_payback) by focusing on creation and explaining the calculation modes.

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 explains the two amount_type modes and advises using them to avoid errors. It does not explicitly mention when not to use the tool or compare with alternatives, but the context is clear for a creation tool.

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