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

With no annotations, the description carries the full burden but leaves critical behavior unexplained: whether the onchain 'Base Mainnet oracle verification' writes a transaction, requires a wallet/credentials, costs gas, or has side effects on the probed endpoint. It also omits rate limits, timeouts beyond the default, and whether probing is safe/read-only.

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 efficient sentence with the action front-loaded and no waste. The trailing oracle-verification clause is efficient in length but introduces unexplained jargon rather than earning its place with detail.

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?

No output schema and no annotations, so the description should explain what an SLA-compliance result and an 'oracle verification' return look like, plus any auth/side-effect requirements. Neither is covered, leaving an agent unable to predict the tool's outcome or cost.

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 coverage is 100%, so both endpointUrl and maxLatencyMs are already documented, and the description's mention of 'latency (ms)' and the 2000ms default adds nothing new. Baseline 3 applies when the schema does the heavy lifting.

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 specific verbs (probe, measure) and resources (live API endpoint, latency, SLA compliance), which clearly separates it from discover_monitored_apis and get_usdc_escrow_contract. The trailing clause about 'Base Mainnet oracle verification' is opaque but does not obscure the core purpose.

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?

No guidance on when to use this tool versus the siblings, no prerequisites, and no exclusions. The only signal is the implied 'probe a live endpoint' framing, which an agent must infer.

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