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

Annotations already declare the tool as read-only, idempotent, open-world, and non-destructive, so the description does not need to establish basic safety. It adds useful scope details beyond annotations, notably that quotes are live but limited to $1-$500 and that the tool reports the largest sale that executes now, yet it does not describe freshness guarantees, rate limits, or how warnings are produced.

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 description is a single dense sentence that front-loads the free GBRIDGE market identity and then lists output categories. It is appropriately sized for a no-parameter tool, though the colon-separated enumeration is somewhat run-on and could be easier to scan if split by output family.

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?

Given that the tool has no parameters, no output schema, and annotations that already cover safety, the description carries most of the burden for explaining what the agent gets back. It reliably enumerates the relevant market data families and includes warnings and fees, but it leaves the relationship to overlapping sibling tools implicit.

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 has zero parameters and the schema is empty, so there are no input semantics for the description to clarify. The baseline for a no-parameter tool is 4, and nothing in the description creates confusion 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 names a specific resource, the GBRIDGE market on Solana, and enumerates the data it covers: verified Meteora DAMM v2 pool, price, liquidity, live buy/sell quotes, largest executable sale, fees, token facts, and warnings. It is clear what the tool provides, but it does not explicitly distinguish this aggregate market view from siblings like gbridge_quote, gbridge_liquidity, and gbridge_token_info, which overlap with the listed outputs.

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 explicit guidance on when to use this tool versus the sibling tools that provide quotes, liquidity, or token information. The 'Free' label and the breadth of included data imply it is a consolidated market overview, but the agent must infer that from the overlapping output list rather than from any stated usage rule or exclusion.

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