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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: two independent data sources (node txpool vs. status page), the fact that either may be missing with its failure surfaced in 'errors', interpretation thresholds (under 0.5 light, over 2 backlog), and the expectation that Parallax's mempool is usually near empty.

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?

Front-loaded with the core concept ('Transactions waiting to be mined') and every sentence carries concrete information about returned fields. It is dense with nested quoted terms but not padded; slightly heavy for a single-status tool, but each clause earns its place.

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 fully carries the burden of explaining return values, and it does so field by field, including the failure-reporting mechanism. Nothing an agent needs in order to call and interpret this zero-parameter tool is missing.

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 the baseline of 4 applies. The description correctly documents the empty input contract implicitly by describing only the returned data, adding no misleading parameter expectations.

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 (mempool) and precisely enumerates what is reported: pending/queued counts, median pending across nodes, 'pressure', blocks to clear, and current gas price. It is clearly distinguishable from siblings like gas_price (single metric) and network_health (network-wide).

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?

The field semantics imply when the tool is useful (assessing congestion/pending load), but the description never states when to prefer it over siblings such as gas_price, network_health, or mining_stats, nor any exclusions. Usage is left to inference.

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