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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, and the description adds genuine context beyond them: the upstream data source, the fact that every tracked operation is re-validated at the latest block (implying one or more live RPC calls per item and non-trivial latency), and that no API key or payment is required. It does not discuss failure/partial-failure behavior when an RPC check reverts or is unavailable.

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?

One dense sentence front-loads the essential fact (live state of tracked pending operations) and then qualifies freshness, source, and cost. It is efficient with no filler, though the parenthetical function list and pricing clause make it slightly cramped for a single sentence.

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 hinting at what comes back, and the named checks (timestamp, pending, done) do imply the shape of each item, while the source URL explains provenance. It still leaves open result ordering, size/caps, and what is returned when the optional protocol filter matches nothing.

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% and the single optional 'protocol' parameter is already documented as a case-insensitive filter against the radar.json item's protocol field. The description adds nothing about the parameter (e.g., matching behavior or results when nothing matches), so the baseline 3 applies.

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 a specific resource and scope: 'Live state of the public pending timelock operations tracked in .../radar.json', plus the concrete re-check calls (getTimestamp, isOperationPending, isOperationDone). That is far more specific than the title, but it never contrasts itself with siblings such as pacta_scan_timelock_op, so an agent must infer whether this list-wide view differs from a per-operation scan.

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?

'Live state ... each re-checked at the latest block' implies the tool is for current, on-chain-verified status rather than cached radar data, and 'Free during the launch (no key, no payment)' signals frictionless access. However, there is no explicit when-to-use/when-not-to-use statement and no named alternative for cases where a single known operation is being inspected.

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