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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile needs no restating. The description adds value by disclosing the derived 'busy/normal verdict' and enumerating the returned snapshot fields, which tells the agent this is a point-in-time read. It does not mention freshness/caching or how the verdict thresholds are computed, keeping it just short of a 5.

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?

Three compact sentences in a consistent what/when/when-not/returns structure, with the core purpose front-loaded. Every clause carries information an agent needs; nothing is redundant with the title or annotations.

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?

There is no output schema, and the description compensates by naming the return fields (txs, bytes, usage_mb, max_mempool_mb, load_pct, min_fee_sat_vb, total_fees_ltc, verdict, fee_rate_histogram). Combined with the annotations and the zero-parameter schema, an agent has everything required to call and interpret this tool.

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 clarify beyond the schema, which yields the baseline of 4. The description correctly avoids inventing parameters or implying required inputs.

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 a specific resource and scope (Litecoin mempool depth, fee-rate histogram, busy/normal verdict) with a concrete verb-like framing of what is reported. It explicitly distinguishes itself from the sibling ltc_get_fee_rates, so an agent can route between the two without inspecting either schema.

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?

Provides an explicit 'When to use' (deciding whether now is a good moment to settle LTC, or gauging backlog depth) and an explicit 'Do not use' with the named alternative for fee selection. Both the selection condition and the exclusion are stated, leaving nothing to inference.

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