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

Annotations already cover readOnly/idempotent/non-destructive/open-world, so the description correctly spends its budget on non-obvious traits: the auth prerequisite, the assurance that Google credentials stay in Trakkr and are never returned, and an important semantic caveat that position is an average across recorded impressions rather than a fixed SERP rank. No return format or pagination detail, but the schema/annotation coverage keeps the bar low.

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?

The prose paragraph is front-loaded and each sentence earns its place. The Args block is mildly redundant, restating url and days semantics already stated above, but it is compact and not padded.

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 return-value burden and does so by listing the metric set and the top-pages/queries scope. Combined with the auth prerequisite and position caveat, an agent has everything needed to call this correctly.

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 only 20%, so the description must compensate and largely does: it explains brand_id (required), url omission vs page URL behavior, days as an inclusive 1-90 window with default 28, and compare_previous_period as equal preceding period with deltas. Only user_intent is left entirely to the schema.

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 a specific verb+resource ('Get Google Search Console performance') and immediately names the data source (Trakkr connection). The second sentence enumerates the exact metrics returned (clicks, impressions, CTR, average position), which differentiates it from generic siblings like get_traffic or get_rankings.

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 concrete when-to-use guidance for the key parameter branch (omit url for property-wide top pages/queries, pass a URL for page-level aggregates) and states the prerequisite that the brand must have connected Search Console in Trakkr. It does not, however, name any sibling tool as an alternative for adjacent metric needs.

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