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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description does add one genuinely useful behavioral fact: positions are bucketed (Top 3, 4-10, 11-20, 21-30, not in top 30) rather than exact, which annotations cannot convey. It says nothing about pagination behavior or what 'tracked' scopes to, so it is useful but not rich.

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?

One compact sentence that leads with the resource and then lists outputs in a tight parenthetical; nothing is padded. It is a sentence fragment with no explicit action verb, which is the only structural weakness.

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 full schema coverage, complete annotations, and an output schema, most burden is already carried elsewhere. However, the description spends its whole budget previewing return fields that the output schema already defines, while omitting scope information an agent would want, such as what 'tracked' searches mean and how fresh the data is.

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%: the site parameter already documents the single-site-optional / multi-site-required rule and the fallback that lists sites, and cursor explains next-page usage. The description adds no parameter-level meaning beyond that, 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?

The description names the resource (tracked Google searches) and enumerates exactly what data is returned: position bucket, change since last check, monthly searches, and alerts. An agent can distinguish this from generic siblings like get_google_overview or get_google_competitors without opening a schema. It stops short of an explicit verb statement or naming the sibling it differs from, keeping it at 4.

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?

No when-to-use guidance, no prerequisites, and no alternatives are mentioned. Nothing tells the agent whether this is the right call versus get_google_overview or get_what_changed when the user asks about ranking movement. Usage is only inferable from the tool name and the returned-field list.

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