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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the data provenance ('read from the contracts'), which is useful context about freshness/source. It does not cover update cadence, coverage universe completeness, or return shape.

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?

It is a single sentence, which is efficient, but the opening rhetorical question ('How much real-world value is on-chain today') delays the actual payload and the parenthetical examples (BlackRock BUIDL, Ondo ...) add length without much selection value. Front-loading could be tighter.

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 zero-param read tool with no output schema, the description does list the data categories covered, which is the main thing an agent needs. However, it says nothing about the response structure, units, or whether the world-market denominators are included, so the agent must discover output shape at call time.

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 zero parameters, so the baseline is 4. The description appropriately spends no words on arguments and instead explains the data content.

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 specific resource (on-chain tokenisation: stablecoins, tokenised treasuries/funds, gold, shares) and the framing metric (value on-chain vs. each world market). An agent can distinguish it from sibling get_crypto_regulation or get_etf_flows. The rhetorical question opening is less direct than a verb-first phrasing, but the content is clear.

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 statement of when to call this versus alternatives, no prerequisites, and no mention of any sibling. The agent must infer usage purely from the subject matter.

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