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

The readOnlyHint annotation already establishes this is a safe read, so the bar is low. The description adds genuine content semantics — that the figure is decomposed into chain-confirmed vs merely agent-declared — but says nothing about how it is computed, how fresh it is, or what the response shape looks like.

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?

Two tight sentences with the key quantity front-loaded. The second sentence is slightly rhetorical ('the point of the whole network') but earns its place by telling the agent to call this early.

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-only tool with no output schema, the description conveys enough about what the caller receives (target plus live, split by confirmation source). An agent can call it confidently; only the precise return structure is left unspecified, which 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?

The tool takes zero parameters, so there are no parameter semantics to explain. Baseline 4 applies per the rubric for a 0-param 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?

The description names the resource concretely: it returns the USD 100,000,000 target plus the live figure, split into chain-confirmed vs agent-declared. That is more specific about content than a generic 'get status', though it uses evocative language ('the point of the whole network') rather than a clean verb+resource and does not name a sibling it differs from.

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?

'Read this first' is an explicit prioritization cue that implies this is the entry-point tool, which is useful guidance in a 40-plus sibling namespace. However, it names no alternatives and gives no when-not conditions, so the routing guidance is implied rather than complete.

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