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

Annotations already declare readOnlyHint and openWorldHint, but the description goes well beyond: it discloses data sources (public RPC plus DexScreener/GeckoTerminal), that third-party market data is 'labelled unverified', that the swap simulation uses eth_simulateV1 with 'no transaction sent', and that 'Unreadable fields are reported as unknown.' These are exactly the operational facts an agent needs before trusting output.

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 opening clause is well front-loaded, but the remainder is one enormous run-on sentence enumerating roughly twenty returned fields. Since there is no output schema, the enumeration earns its place, yet it would read far better as a structured list rather than a comma-spliced block.

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 tool with no output schema, the description compensates well by enumerating the returned facts, naming the data sources, and stating coverage limits. The only missing operational detail is cost/latency for what is clearly a heavy multi-API call.

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?

With one parameter at 100% schema description coverage, the baseline is 3. The description adds only the chain context (chain ID 4663) and the 0x-address assumption; the format itself is already fully specified by the schema pattern.

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?

Opens with a specific verb and resource: 'Read-only on-chain facts for one 0x contract address on Robinhood Chain (chain ID 4663).' The scope (single contract, specific chain) is unambiguous and clearly distinct from the sibling overview/disclaimer/links tools.

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?

Explicitly bounds the tool with negatives: 'Not a safety verdict, not an audit, no guarantee; other DEX designs and liquidity locks are not covered.' This tells the agent when the result should not be relied on. However, it never names a sibling alternative or a triggering condition (e.g. 'use get_bully_overview for the official contract'), leaving routing to inference.

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