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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to cover safety. It adds useful behavioral context by stating data is read on-chain on Robinhood Chain and that the price comes from DexScreener, while also listing the returned metrics.

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 one efficient, front-loaded sentence that states the usage condition first, then packs in all return values and data sources with no filler. It does not waste words or restate the title.

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 simple, read-only tool with no output schema, the description provides a complete return contract: it lists each metric, notes shares of supply, and names both data sources. An agent has enough information to know what to expect without additional lookup.

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%, so the optional quote parameter is fully documented by the schema itself. The tool description adds no additional meaning about that parameter, which is acceptable at the baseline but not a differentiator.

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 clearly states the tool's purpose: retrieving the current state of the $SWOGE token economy, and enumerates the exact data points returned (supply, burned amount, vault balance, staking APR/cap, price). It is specific about the resource and sources, though it does not explicitly differentiate itself from sibling tools like scan_token.

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 opens with 'Use this when you need...' and gives a precise trigger condition. It does not mention when not to use it or name an alternative tool, but the condition is specific enough to guide an agent effectively.

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