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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by enumerating the returned content (vault addresses, per-chain deposit assets, explorers, RPCs, faucets), but says nothing about auth requirements, freshness, or whether these are live mainnet/testnet values.

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?

A single front-loaded sentence with no filler, and the most useful content (networks, vault addresses, deposit assets) comes first. It is a dense run-on list, but every clause carries information.

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 return contents, and it does so explicitly by listing vault addresses, assets, explorers, RPCs and faucets. Missing only chain/environment disambiguation against the info siblings, which is minor for a read-only reference tool.

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 100% and the single enum parameter already documents both values plus the 'omit for both' behavior. The description never mentions the network filter, so it adds no meaning beyond the schema. Baseline 3 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?

States a concrete resource (Gloam's networks) and enumerates the payload: vault/pool addresses, deposit assets per chain, explorers, RPCs, and faucets. An agent knows exactly what this tool returns. It does not, however, distinguish itself from the sibling gloam_info or gloam_vault_stats, which plausibly overlap.

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 is purely declarative and gives no when-to-use guidance, no exclusions, and never mentions the sibling tools it might be confused with (gloam_info, gloam_vault_stats). The only routing hint ('Leave out for both') lives in the schema, not the description.

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