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

Annotations already establish the safe read-only, idempotent, non-destructive profile, so the bar is lower. The description does add return-content context not covered by annotations (per-loan limits, leverage flag, a lend-asset column appearing conditionally 'once there is more than USDG'), but with no output schema this remains cryptic and jargon-heavy rather than clear behavioral disclosure.

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?

It is a single compact sentence with the core purpose front-loaded, which is good, but the trailing clause structure ('a row names the lend asset it is borrowed in, once there is more than USDG') is convoluted and hard to parse on first read.

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 zero-parameter read-only listing with no output schema, the description carries the full burden of explaining what comes back. It gestures at the return shape but leaves the conditional field and the meaning of 'USDG'/'leverage buys them' underspecified, so an agent has only a partial picture.

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 tool takes zero parameters and schema coverage is 100%, so there is nothing for the description to compensate for. Baseline of 4 applies.

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 names a concrete resource (tokens accepted as collateral) and the specific attributes returned (per-loan limits, leverage eligibility), so the agent knows what it is fetching. It does not explicitly differentiate itself from siblings like gage_borrow_quote or gage_portfolio, and the phrasing 'gage takes as collateral now' is a bit obscure, but the purpose is inferable.

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 explicit when-to-use or when-not-to-use guidance is given, and no sibling (e.g. gage_borrow_quote, gage_leverage_quote) is named as an alternative. Usage is only implied by the fact that it is a zero-parameter reference listing of collateral assets, which an agent would call when it needs collateral metadata.

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