get_vault_loan

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

With no annotations, the description carries the full burden. It discloses key behaviors: automatic indirection handling and null return for inactive loans. Although it doesn't explicitly state read-only nature, the verb 'Get' implies non-destructive behavior, and no contradictions exist.

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?

Two sentences, fully front-loaded. Every word serves a purpose: action, special handling, and edge-case return. No waste.

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 simple getter with one optional parameter and no output schema, the description covers essential behavioral aspects (indirection, null return). It lacks output structure details, but given the tool's simplicity and sibling context, this is acceptable.

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%, so the schema already documents the 'wallet' parameter with default behavior. The description adds no additional meaning beyond schema, meeting baseline. No extra detail is needed.

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: 'Get full loan details for an active vault loan.' It distinguishes itself from siblings by specifying 'vault loan' and mentioning automatic indirection handling. The return behavior (null if none) is explicit.

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 clear usage context: handles vault-as-borrower indirection and returns null when no active loan exists. While it doesn't explicitly compare to sibling tools, the purpose is specific enough for an agent to decide when to use this tool over others like get_loans or get_user_loan_details.

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