extend_loan

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

With no annotations, the description must disclose behavioral traits. It only states the action and cost benefit, failing to mention side effects, safety, or whether the operation is destructive. It does not indicate if permissions are required or what changes occur.

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 very concise with two sentences. The first sentence states the action, the second adds a key benefit. No unnecessary words, though it could be slightly more structured to hint at parameters.

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 five parameters and no output schema or annotations, the description is incomplete. It doesn't explain how to specify the loan (loan_type and hub_id), what 'days' means, or what the output is. The agent lacks enough context to use the tool confidently.

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 description coverage is only 40% (2 of 5 parameters have descriptions). The description adds no parameter-level meaning; it mentions 'vault or hub' which is already in the schema enum, but doesn't explain 'days', 'hub_id' beyond the schema, or 'refinance'.

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 extends vault or hub loans, with a specific verb and resource. It distinguishes the action from taking a new loan, though it does not explicitly differentiate it from sibling tools like 'extend_vesting' or 'take_loan'.

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 usage when extending an existing loan rather than taking a new one, citing cost savings. However, it lacks explicit guidance on when not to use it (e.g., if the loan is not extendable) or alternative tools.

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