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

readOnlyHint=true already establishes this as a safe read, so the description's added value is modest. It does disclose the return content (status plus last test date) and enumerates the possible status values, which goes slightly beyond the annotations, but says nothing about what the values signify, freshness, or whether a failed test is indicated.

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?

Two short sentences, front-loaded with the return payload and followed by the actionable cue. No filler, no restatement of the tool name, and the parenthetical defining the status values earns its 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-parameter read-only status check with no output schema and safety fully covered by annotations, the description supplies everything needed to decide to call it and what to expect back. It stops short of explaining how to interpret Clear/Cloudy/Stormy, which is a minor gap.

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 the single parameter already documents that it accepts a connector name or slug with an example. "By name" in the description merely echoes this, adding no new semantics, so the baseline 3 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?

States a specific resource (a connector, identified by name) and what is returned: a status value plus the last test date. It is distinguishable from siblings like list_connectors and compare_connectors, though the nonstandard term "Connector Weather" requires the parenthetical to be interpretable.

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?

"Check this before relying on a connector" gives a clear when-to-use cue, but there is no when-not guidance and no sibling is named as an alternative, even though get_connector_report and compare_connectors plausibly overlap. Usage is implied rather than delimited.

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