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

Annotations already declare readOnlyHint and openWorldHint, but the description adds material facts an agent cannot see elsewhere: only the current 'now' state is returned, history requires external archiving, and calls cost $0.002 USDC via x402 with failures not charged. Cost and billing-path disclosure for a paid endpoint is exactly the kind of context the safety annotations do not cover.

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?

Scope is front-loaded, but the body is cluttered by opaque internal references — '(ARSIV-GEREKLI)' and 'per ARACLAR.md specification' — that mean nothing to an agent and read as untranslated noise. The sibling listing is useful but wordy for two tools; trimming would sharpen it without losing routing value.

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 an output schema present and zero parameters, the description's job is scope, limits, and cost, all of which are covered. The only remaining gap is operational: no hint about data freshness, latency, or rate limits for a 'live' endpoint that is billed per call.

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 schema has zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a parameterless snapshot call rather than one requiring a time window or node selector.

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 first sentence names the resource (Kaspa mempool) and enumerates the exact payload: unconfirmed transaction count, node sync status, priority feerate. That is specific enough for an agent to distinguish it from crypto_kaspa_dag_state and crypto_kaspa_fee_regime without opening any 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?

It routes explicitly to alternatives with the selecting condition: crypto_kaspa_dag_state 'when you need Kaspa BlockDAG snapshot' and crypto_kaspa_fee_regime 'when you need fee market regime classification'. It also states a when-not constraint — no historical data is available from public nodes — so the agent knows not to call it for time-series.

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