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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds worthwhile provenance (BitBasic's hourly readings) and aggregation semantics (month-end snapshot with range and prior-month delta), but omits any note on data latency, caching, or how partial months behave.

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 metric list and trails provenance last; every clause carries information. The nested parenthetical about staking providers makes it slightly harder to parse than a short structured list would be.

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?

With no output schema, the description carries the burden of describing returns and does so well: it names the four metrics plus range and month-over-month delta. What remains unstated is minor — metric definitions (e.g. what higher Nakamoto means) and whether staking-provider breakdown appears for all networks, which it hedges as 'where it has them'.

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?

Schema description coverage is 100%, so both parameters are already documented, establishing a baseline of 3. The description clarifies that figures are measured 'at the month's end' with a prior-month comparison, which marginally sharpens what the month value selects, but it says nothing about the network parameter beyond the schema's own 'slug from list-networks' note.

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 (monthly stake-concentration report) and enumerates the concrete metrics returned: Nakamoto coefficient, top-10 share, HHI, active set, plus range and month-over-month change. That level of specificity clearly separates it from siblings such as network-status or network-parameters, though the phrasing is noun-heavy rather than a verb+resource statement.

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 only implied: an agent can infer this is the tool for concentration/decentralisation metrics, but the description never states when to prefer it over siblings or any preconditions. It does not mention that the network slug must come from list-networks (that lives only in the schema).

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