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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds real value by disclosing that results include third-party data (Jupiter verification and organic score) and external links, but says nothing about caching, rate limits, or whether the authority fields can be null.

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 compact sentence with the cost signal front-loaded followed by a scannable field list. The enumeration is dense but every item describes a distinct returned datum, so nothing is wasted.

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 whole burden of telling the agent what comes back, and it does so thoroughly as a field list. Minor gaps remain around nullability and freshness of third-party scores.

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 no parameters, so there is nothing for the description to disambiguate beyond what the schema provides. The baseline of 4 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?

Names the resource (GBRIDGE token) and enumerates the exact facts returned: mint, supply, decimals, authorities, verification score, holders, and explorer links. This implicitly separates it from siblings like gbridge_market and gbridge_liquidity (market/pool data), though it never states that contrast explicitly.

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 'Free:' prefix hints at a cost distinction, but there is no statement of when to call this versus gbridge_market, gbridge_quote, or gbridge_liquidity, and no prerequisites or exclusions. An agent must infer the choice 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.