Get protocol stats

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety and determinism profile is covered. The description adds the useful detail that this is protocol-wide (not scoped) aggregation, but says nothing about freshness, caching, or cost despite openWorldHint=true.

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 dense sentence that front-loads the aggregating scope and then lists categories. The list is long but each item is a distinct returned metric, so little 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?

For a zero-param, well-annotated read tool with no output schema, the description is nearly complete: it enumerates what the aggregate contains. It stops short of explaining aggregation granularity or whether 'estimated value' is per-chain, but that is a minor gap.

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?

Zero parameters, so there is nothing to disambiguate and the baseline is high. The description correctly signals that the call needs no inputs via its protocol-wide framing.

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?

States a specific verb (Get) and resource (protocol-wide statistics) for the named platform, and enumerates the exact categories returned (properties, value, lending volume, DeFi pool TVL, geography, contract addresses). This distinguishes it from query-shaped siblings like get_lending_market or search_properties.

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?

Usage is implied: call it for a protocol-wide aggregate. But there is no explicit when-to-use vs. siblings like get_lending_market (which covers lending specifics) or get_valuation. An agent must infer the aggregation scope on its own.

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