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

Annotations already establish readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: this is a real-time estimate, it includes empirical recent payment data, and it quantifies mempool congestion. It does not state the freshness/staleness window or units, but it meaningfully enriches the picture.

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 sentence with a front-loaded definition of the tool's subject, followed by a tight colon-separated list of the returned data. Zero filler; every clause names a distinct piece of information the caller receives.

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 input schema and no output schema, the description is the only source of return-value information, and it does enumerate the four content categories. It omits units/formatting and the recency basis of 'lately,' so it is good but not exhaustive for a tool whose entire contract lives in prose.

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 is nothing for the description to disambiguate. The baseline of 4 applies; no parameter-level detail is needed or expected.

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 gives a specific resource — current DOGE fee conditions — and enumerates the four concrete data points returned (minimum relayable payment, recent paid fees, next-block rates, pending transaction count). It is clearly distinct from siblings like get_block, get_transaction, and get_network, which cover different resources.

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?

'right now' implies this is a live-snapshot lookup, so the agent can infer it answers 'what will it cost to send DOGE at this moment.' There is no explicit when-to-use statement, no exclusions, and no named alternatives, so usage guidance is only implied.

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