health

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

With no annotations, the description carries the full burden, and it does add genuinely useful behavioral context beyond the name: fetches are limited to public pages and require a home/residential machine. It does not say whether the call is read-only/side-effect free or what a degraded/non-ready response implies, so the disclosure is partial rather than complete.

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 short sentence with no filler, and the two substantive items (engine inventory, limits) come first. The framing clause 'What this connector can do right now' is slightly indirect where a direct verb would be tighter, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the description supplies the one thing structured fields cannot: the environmental constraints (public pages, residential host). For a zero-parameter diagnostic tool this is close to sufficient, missing only a cue on when to call it.

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 tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to clarify about arguments. The description correctly focuses on what the call surfaces instead of inventing parameter details.

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 says the tool reports which fetch engines are installed plus the connector's limits, which is a recognizable resource, but it is phrased as a capability statement ('What this connector can do right now') rather than an explicit verb+resource like 'Report connector health and installed fetch engines'. It implicitly distinguishes itself from the fetch siblings by being about the connector itself rather than fetching, but never names them.

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 explicit when-to-use statement, no mention of the amazon_fetch / amazon_product siblings, and no precondition such as 'call this before fetching to confirm an engine is available'. The agent must infer that this is a diagnostic/probe tool from the content alone.

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