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

Annotations already declare readOnlyHint, openWorldHint, and non-destructive behavior, so the description only needs to add context. It does supply useful aggregation semantics: this is a one-call rollup combining two otherwise separate data sources, which the annotations cannot convey. It does not discuss rate limits or freshness of the GSC headline, keeping it short of a 5.

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 sentences, zero filler, and the value proposition (what you get) is front-loaded ahead of the routing guidance. Every clause earns its place.

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?

No output schema exists, so the description carries the return-value burden, and it does describe the payload at a high level (profile fields plus GSC headline). It does not spell out the full shape of the profile or the Search Console metrics returned, which leaves a minor gap for a read-only orientation tool.

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%, with the "detail" verbosity parameter fully documented in the schema (concise vs. detailed truncation behavior). The description does not restate or extend parameter meaning, which is the correct baseline when the schema does the heavy lifting.

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 (orientation for a site) and enumerates the concrete content delivered: profile (domain, industry, USP, integrations) plus a Search Console headline. It distinguishes itself from get_site and get_gsc_metrics by name, so an agent can route without opening either schema.

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?

Explicitly says when to use it ("Use this first to understand a brand") and names the alternatives it replaces ("instead of chaining get_site + get_gsc_metrics"). This is the rare definition that gives both a trigger and a named substitute.

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