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

With no annotations provided, the description carries full burden. It discloses the list of included metrics, which is useful, but does not elaborate on data freshness, aggregation, or whether the output is a simple snapshot or a detailed report. This is a read-only overview, so the lack of side-effect disclosure is acceptable, but more contextual detail would improve transparency.

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 a single sentence that front-loads the tool's purpose and then concisely lists the included metrics. Every word earns its place; there is no redundancy or filler.

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?

Given the tool's low complexity (no params, no output schema), the description adequately conveys what the tool returns by listing the key ecosystem metrics. It lacks explicit mention of output format or data recency, but for a simple overview tool, this is a minor gap and the description is sufficient for an agent to select and invoke it 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?

The tool has zero parameters, and the schema description coverage is 100% (vacuously). The description adds no parameter-specific meaning, but since there are no parameters, the baseline of 4 applies. No additional information is needed.

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 provides a Sui ecosystem overview, enumerating the specific data points it covers (SUI price, TVL, protocol count, validators, transactions). This distinguishes it from sibling tools that focus on narrower domains like bridge flows or DEX volume.

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 implies usage for a high-level ecosystem snapshot but does not explicitly state when to prefer this tool over the more specific sibling tools. The presence of sibling tools covering individual metrics suggests a general use case, but no direct exclusions or alternatives are mentioned.

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