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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the payload contents but says nothing about data freshness (live vs snapshot), rate limits, or whether the 'largest executable sale' is computed against current liquidity — context that matters for a trading-data read.

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 front-loaded sentence that enumerates the three returned data categories without redundancy. The 'Free:' marketing prefix is the only expendable element.

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 parameters and no output schema, the description carries the return-value burden and largely discharges it by naming the three things returned. It is slightly incomplete on data freshness and on how 'by size' is parameterized or bucketed.

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 nothing to disambiguate; the description correctly frames the result as unfiltered pool-wide data by size. Baseline for a no-parameter tool 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 specific resource (GBRIDGE pool liquidity) and the concrete outputs: available liquidity, sell quotes by size, and the largest executable sale. It is clear what the tool returns, though it never distinguishes itself from the overlapping siblings gbridge_quote and exit_check.

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?

Usage is only implied — an agent can infer this is the tool to call before sizing a sale — but there is no explicit when-to-use or when-not-to-use, and no pointer to gbridge_quote or exit_check as the alternatives for related questions.

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