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

Annotations already declare the safe-read profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds material context: browser-session auth, owner-only authorization, realtime-updating data, and explicit privacy exclusions (no user identity, typed text, or screen recording). The privacy note tells the agent what it will NOT receive, which is genuinely useful for framing answers.

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?

Short declarative sentences, front-loaded with what is read and the time window, then constraints, then data-freshness and privacy. Every sentence carries distinct information with no restatement of the name or annotations.

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 single-parameter, read-only tool with no output schema, the description covers what data is returned, the freshness model, the auth/permission gate, and privacy boundaries. An agent has everything needed to decide to call it and to describe the result responsibly.

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 (id = "Owned Site.id.") is fully documented in the schema, including the ownership tie-in the description already asserts. The description adds no format, range, or syntax detail beyond this, so 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?

The description names a specific verb ("Read") and a concrete composite resource set: installation, actions, paths and the ordered conversion funnel, scoped to the last seven days for the owned site. No sibling (audit_site, get_site, search_console) covers journey/funnel data, so the agent can distinguish it without opening schemas.

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?

It states clear preconditions and audience: "Requires the account's browser session" and "Only this site's owner can read it." The seven-day window also implicitly bounds when the tool is the right source. It stops short of naming an alternative tool or an explicit when-not-to-use condition, so it is strong context rather than full routing.

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