postCryptoLoanFixedRenew

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

No annotations are present, so the description must carry the full burden. It adds a rate limit disclosure ('1 request per UID') but does not detail side effects like what happens to the old loan or collateral. Some behavioral insight is provided 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?

The description is well-structured with clear sections (Features, Use Cases) and is concise, using bullet points and short sentences. Every sentence adds value without unnecessary verbosity.

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 no output schema and no annotations, the description covers purpose, use cases, rate limit, and parameter hints. It lacks details on return values or prerequisites but is sufficient for a renewal tool. Slightly more could be said about preconditions.

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 0%, so the description compensates by explaining that 'collateralList' is for adding additional collateral and 'loanId' is the existing loan. This adds meaning beyond the raw schema, helping an agent understand parameter usage.

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 explicitly states 'Renew an existing loan by creating a new loan to repay the old one' and lists features and use cases, clearly identifying the tool's purpose and distinguishing it from sibling tools like renewFixedBorrow.

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?

Use cases are provided ('Extend loan term to avoid liquidation', 'Add more collateral to improve LTV'), giving clear context for when to use. However, it does not explicitly mention when not to use or compare to alternative tools.

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