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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description adds meaningful behavioral context by naming the live-data nature, the external sources (DexScreener, GoPlus, SWOGE AI colony), and the conditional Robinhood Chain behavior. It does not mention rate limits or failure modes, but annotations already cover the safety profile.

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 sentence delivers the core action, the exact input, and a structured breakdown of outputs with no filler. The key information is front-loaded and every phrase adds value.

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 read-only tool with no output schema, the description covers the essential input requirements and the categories of returned data, including a conditional edge case. It does not specify return shape or formatting, but an agent has enough to select and invoke the tool correctly.

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%, with both parameters already well documented. The description reinforces the address format and adds context about what the address is used for, but it does not add meaning beyond the schema for the 'quote' parameter. Baseline 3 is appropriate.

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 uses a specific verb ('Read live data on a token') and a clear resource ('by its EVM contract address'), then enumerates the exact data categories returned: market, contract security, and SWOGE AI colony observations. This clearly distinguishes it from sibling tools like web_search or wallet_intel.

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 gives clear context for when to use the tool: whenever a caller needs live market, security, or AI colony data for a specific EVM token address. It does not explicitly name alternatives or exclusion cases, but the intended use case is strongly implied.

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