vault_borrow

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

With no annotations, the description must disclose behavioral traits. It only reveals the interest rate (2% + 0.005%/day) but omits critical details like loan mechanics, repayment terms, or what happens in case of default. For a mutating financial tool, this is insufficient.

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 extremely concise, using one sentence to convey the core function and a critical behavioral detail (interest). It is front-loaded with the verb and resource, earning its place without extraneous text.

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 the absence of output schema and annotations, the description is incomplete. It fails to mention return values, side effects, or necessary context for a borrowing tool, such as the creation of a loan or repayment requirements.

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% with clear parameter descriptions ('STASIS amount to borrow against', 'Loan duration'). The description adds no additional meaning beyond what the schema provides, maintaining the baseline score.

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 action ('Borrow USDB') and the resource ('locked wSTASIS'), including interest rate details. It effectively differentiates from sibling tools like 'vault_repay' by specifying borrowing as the core function.

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 provides no guidance on when to use this tool versus alternatives, such as 'take_loan' or 'vault_repay'. It also does not mention prerequisites (e.g., having locked wSTASIS) or typical scenarios.

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