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

The description says 'Read-only' and 'live', which conveys safety and freshness. With no annotations provided, the description carries the burden, and it does disclose the read-only nature and the conservative profile limitation. It doesn't mention rate limits, caching, or what 'conservative' means exactly.

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?

One short sentence with no filler. The key facts—live, Forge vault TVL, Base, conservative profile, read-only—are all front-loaded and every word earns its place.

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 tool, the description is mostly sufficient. However, there is no output schema and no mention of return format or units (e.g., USD, wei), and 'conservative profile' is vague. An agent might call it correctly but not know how to interpret the result.

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?

There are zero parameters, so the schema is trivially complete. The description adds context about what the returned stat represents (live TVL on Base, conservative profile), which is useful despite no params.

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 specific verb ('Get') and resource ('live Forge vault TVL on Base'), and notes the conservative profile in MVP. It is distinguishable from siblings like get_current_apy and get_balance, though it doesn't explicitly name them.

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?

Implies usage as a read-only stats query, and the 'conservative profile in MVP' hints at a scope limitation. However, it doesn't explicitly say when to use this over get_current_apy or get_balance, nor when not to use it.

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