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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that results are 'live' and chain-scoped to Base, but says nothing about data freshness, upstream rate limits, or what an 'executable' path guarantees — gaps that matter for a live telemetry oracle.

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 dense sentence with no filler, and the read-only/scope qualifiers are front-loaded. 'Telemetry oracle' is slightly jargon-heavy but does not waste space.

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?

For a one-optional-param, well-annotated tool this is close to sufficient, but with no output schema the description should sketch the shape of returned route/discrepancy data. It also omits any explanation of the threshold parameter, leaving real gaps.

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 0% for the single parameter min_spread_bps, and the description never mentions it. An agent gets no clue what the unit is, whether 10 bps is the floor for inclusion, or how the default affects results, so the description fails to compensate for the schema gap.

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 verb and resource: calculates live cross-DEX price discrepancies and executable smart-router paths, scoped to Base. That is concrete enough to separate it from siblings like pulse_base_liquidity and pulse_threat_intel, though it never names or contrasts them explicitly.

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?

There is no statement of when to call this versus pulse_base_liquidity or the other siblings, and no prerequisites or exclusions. The agent must infer usage from the purpose sentence alone.

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