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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds valuable behavioral context by disclosing the $0.10 USDC cost and the specific telemetry dimensions checked, which goes beyond what the annotations provide.

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?

The description is a single, tightly packed sentence that front-loads the tool's purpose ('Pre-flight Arc Mainnet telemetry') and then lists the key outputs and cost. Every element earns its place with no filler or redundancy.

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?

Given the low complexity (two optional booleans), rich annotations, and the presence of an output schema, the description is nearly complete. It communicates purpose, cost, and the data returned. It could be slightly more explicit about when to use it relative to sibling telemetry tools, but that gap is minor.

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 both boolean parameters have clear descriptions in the schema. The tool description does not add additional meaning about the parameters, but the schema already carries the full burden, so a baseline score of 3 is appropriate.

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 clearly identifies the tool as a pre-flight telemetry query for Arc Mainnet and lists the exact data points returned (RPC latency, gas prices, USDC balance, nonce). It is specific about the resource and metrics, though it does not explicitly differentiate itself from sibling tools like arc_analytics or arc_dex_oracle.

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 word 'Pre-flight' provides clear usage context: this tool is meant to be called before performing operations on Arc Mainnet to check network health and account readiness. It does not name alternatives or state when not to use it, but the context is unambiguous enough for an agent to select it appropriately.

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