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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so 'Read-only' in the description is a restatement with no added value. The genuinely useful behavioral content is the enumerated metric list, which partially substitutes for the missing output schema. It does not say whether figures are lifetime cumulative or a current snapshot, nor any refresh/freshness semantics.

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 front-loaded sentence listing the returned metrics, followed by a two-word safety note. Every phrase carries information and nothing is buried or padded.

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-parameter, closed-world stats tool with no output schema, the description does the essential job of telling the agent what comes back. The remaining gap is interpretive: no units, no indication of whether totals are lifetime or point-in-time, which matters for reporting numbers 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 takes zero parameters and the input schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless tool.

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 resource ('Protocol totals') and enumerates the exact metrics returned: volume, fees, open interest, $KYTE burned/staked, staker count, active and total offers. This distinguishes it from per-entity siblings like get_activity or get_positions without naming them. It stops short of 5 only because it never explicitly contrasts itself with a sibling.

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 explicit when-to-use or when-not-to-use statement, and no alternative tool is named. Usage is only implied by the phrase 'Protocol totals', which signals a whole-protocol aggregate rather than a per-user or per-offer query. An agent can infer the scope but gets no routing help against siblings such as get_prices or get_rewards.

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