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

With no annotations, the description carries the behavioral burden and does disclose the returned payload and per-call cost ($0.002 USDC). It does not explicitly state that the call is read-only or describe response units, but 'health' plus the listed fields strongly imply a safe, no-parameter read.

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 one compact sentence followed by a one-sentence pricing note. Every phrase earns its place, and there is no duplication of schema content or filler.

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 no-parameter health endpoint, the description provides enough to invoke it correctly: it names the network, lists the returned fields, and warns about payment. It omits minor output details like gas price units, but this is not critical for a simple health check.

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?

This tool has zero parameters, so the input schema already fully defines the call. The description adds no parameter-specific details, but none are needed; the baseline for a no-parameter tool 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 clearly identifies the resource as Polygon network health and enumerates the exact returned fields (chain id, latest block, gas price, native token USD price). This is specific enough to distinguish it from sibling tools like polygon_balance or polygon_tx, though it does not explicitly name an alternative or use a verb.

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 guidance on when to use this tool versus metric-specific siblings such as polygon_gas, polygon_block, or polygon_token. The only selection signal is 'Cheapest call,' which addresses cost rather than task fit or alternatives.

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