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

Annotations declare destructiveHint=true and readOnlyHint=true simultaneously, and the description gives no hint of any destructive behavior — it reads purely as a read/report tool. The description enriches behavior by disclosing the tracking lifecycle states (awaiting_live, tracking, no_search_console, no_page_identity) and the fixed measurement windows, which is genuinely useful, but it never explains or reconciles the destructive annotation, leaving an agent with a serious unexplained conflict.

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 core question, then packs metrics, time horizons, baseline comparison, tracking trigger, and status enum into a compact paragraph. Dense but every clause carries information; the inline enum list at the end is a bit terse and slightly hard to parse.

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 read-only reporting tool with no output schema, it explains metrics, horizons, comparison baseline, and lifecycle states well. But it omits how results are returned/shaped and, more importantly, leaves the destructive hint unexplained, so an agent lacks enough to fully reason about side effects.

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?

Only one parameter, brief_id, with 100% schema coverage, which is the baseline-4 case for a zero/near-zero-param tool. The description adds context by tying the brief to publication events and the tracking window, though it doesn't spell out what a valid brief_id looks like beyond the schema's 'The brief ID'.

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?

Opens with the concrete question 'Did this published piece rank?' and then enumerates the exact metrics returned (clicks, impressions, CTR, position, top queries) at specific time horizons. An agent can distinguish this from siblings like get_content_brief or check_tracked_keyword_rankings because the resource is scoped to a single published piece keyed by brief_id.

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 implies usage: call this after a brief has been published to check search performance, and it names update_content_brief(published_url=...) as the trigger that starts tracking. It does not explicitly state when NOT to use it or name the sibling tool (content_outcomes / get_gsc_pages) an agent should prefer for other cases, keeping it below a 5.

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