Lends Prepare Accrue Fee

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

Annotations already establish readOnlyHint=true and idempotentHint=true, so the description does not need to restate safety. It adds the useful detail that the transaction is permissionless and that the tool constructs a transaction rather than executing one. However, it does not disclose what executing the fee-accrual transaction would actually change or whether any prerequisites exist. No contradiction with annotations.

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 a single front-loaded sentence with no filler words. It earns its place by immediately naming the action and the 'permissionless' qualifier. It is concise, though the brevity contributes to the lack of parameter and usage detail.

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?

With two required parameters, no schema descriptions, and no output schema, the description leaves critical gaps. It does not define the roles of borrower and collateral, mention the return value, or explain what the constructed transaction is used for. Annotations cover safety but not the operational details needed to invoke the tool correctly.

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?

The input schema has 0% description coverage, so the description must compensate by explaining the two parameters. It never mentions borrower or collateral, leaving their exact meaning unclear. An agent would not know whether 'collateral' refers to a collateral asset address, a vault identifier, or something else.

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?

States a clear verb and target: 'Construct a permissionless vault fee-accrual transaction.' The permissionless qualifier and fee-accrual target distinguish it from other prepare tools like lends_prepare_borrow or lends_prepare_withdraw. The resource is specific enough for an agent to recognize what the tool does.

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?

No guidance is provided about when to use this tool versus alternatives. It does not explain that fee accrual is a maintenance action or when a vault is eligible for it. An agent must infer usage entirely from the tool name and one-sentence description.

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