Check which integrations the project has

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

Annotations only cover readOnlyHint/openWorldHint; the description adds real behavioral semantics: what `connected: false` means versus `reason: sync_failing`, that the figures in downstream tools would be stale, and that Google/sitemap siblings explain the failure. It also discloses scope limits (no CMS integration; WordPress/Laravel are collector install paths reported under `botLogs`), which preempts a plausible misreading.

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?

Front-loads the one-sentence purpose, then the routing rule, then field semantics, then edge-case exclusions — a sensible ordering. It runs a bit long, and the final WordPress/Laravel sentence is the softest, but each sentence carries a distinct disambiguating fact and none is redundant.

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?

With an output schema present the description needn't restate return structure, yet it still explains the semantics of the two output signals an agent is most likely to misread. Combined with the sibling routing and the explicit scope exclusions, an agent has everything needed to call this tool correctly and interpret 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 is 4; there is no parameter syntax for the description to add. The description instead clarifies the implicit 'active project' scope, which is the only input-like thing that matters here.

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 verb and resource — reports whether Search Console, Google Analytics, the bot tracker and the sitemap are connected to the active project — and explicitly distinguishes itself from the traffic/reporting siblings by describing itself as a single connectivity check. An agent can tell at a glance this is a precondition/diagnostic tool, not a data tool.

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?

Gives an explicit when-to-call rule ('call it before reporting a zero or an empty list from get_search_performance, get_ai_traffic, list_bot_visits, count_bot_visits or list_crawls') and explains the failure mode it prevents. It names four concrete alternative tools and the exact condition that selects this one, leaving nothing to inference.

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