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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety and caching profile is covered without description help. The description adds useful behavioral context beyond that by noting it reports current live state (whether the registry still lets it lend, whether deposits/payouts are possible now, what the reserve can pay out now), but says nothing about result volume, freshness, or pagination for a global listing.

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 entire definition is a single long comma-spliced run-on sentence that is hard to parse, with opaque fragments like "the release's and those curators opened" and "its mandate, in plain words in funds". The field enumeration is front-loaded in a way that buries the actual purpose statement, so the sizing problem is structure rather than sheer length.

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 no output schema, the description carries the burden of describing returns, and it does enumerate the attributes (size, free cash, loans out, share value, fee, curator, funded pools, registry status, deposit/payout flags, reserve specifics). That enumeration is valuable, but several phrases are too garbled to tell an agent what a field actually means, leaving the return shape only partially complete.

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, so there is no parameter semantics to explain and the baseline is 4. Nothing in the description misleads about inputs.

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 opens with a defining relative clause ("The LP vaults that lend against LP positions") but never states an explicit verb such as "list" or "return", so the agent must infer that this is a read/list tool over LP vaults. It also never distinguishes itself from closely named siblings like gage_earn_vaults or gage_vault_free_cash, even though the LP-vs-earn distinction is the whole point of the tool.

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?

There is no when-to-use guidance at all: no statement of when to call gage_lp_vaults versus gage_earn_vaults, gage_vault_free_cash, or gage_lp_positions, and no preconditions or exclusions. The agent is left to infer usage purely from the field list.

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