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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds meaningful context beyond them: the 28-day-vs-prior-28 comparison window, that results are DERIVED rather than raw, the connection prerequisite, and the built-in `action` field on headline_insight. No rate limits or pagination behavior disclosed.

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-loaded with the tool's identity and scope, and every clause maps to a distinct insight category rather than filler. It is dense and run-on, but nothing is redundant or padding.

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 no output schema, the description carries the full burden of describing what comes back, and it does so exhaustively (insight categories, action field, comparison window) plus prerequisites and next-step workflow. An agent has everything needed to decide to call it and interpret the response.

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 parameters (site_id, detail) are documented in the schema itself, including the concise/detailed behavior and top-25 trimming. The description adds no additional parameter meaning, 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 verb+resource (DERIVED traffic insights for a brand from Search Console + GA4, last 28 days vs prior 28) and enumerates the exact output categories: striking-distance keywords, CTR underperformers, cannibalization, branded split, AI-referral traffic. This is clearly distinguishable from sibling raw-data tools like get_gsc_metrics, get_ga_metrics, or seo_insights.

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 a real prerequisite ('Requires GSC and/or GA4 connected'), signals cost ('Free read'), and prescribes follow-up actions (rewrite titles via wp_update_page, refresh decaying pages). It does not explicitly name the alternative tools (seo_insights, get_gsc_metrics) or state when not to use it, so not a 5.

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