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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it is empty until Search Console is connected, it is free, and each item ships with a suggested action and supporting evidence.

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-loaded with what it returns, then prerequisite, cost, and next action. No filler; even the one-word 'Free.' earns its place as decision-relevant information.

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 must convey return shape, and it does: recommendation types with a suggested action and supporting evidence. Combined with the connection prerequisite and routing guidance, an agent has nearly everything needed, though ordering and pagination behavior of the list are undocumented.

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%, so both parameters (site, limit) are already fully documented in the schema with defaults and bounds. The description adds no parameter-level detail beyond that, so the baseline of 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?

States a specific verb (get/derive recommendations) and resource (Google Search Console recommendations) and enumerates the concrete content types returned: queries close to page one, pages losing clicks, cannibalization. This distinguishes it from raw-data siblings like get_keywords or get_rankings, which return metrics rather than actionable recommendations.

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 states the prerequisite ('Empty unless Search Console is connected') and routes the agent to next steps: add_to_plan for a new article or the updates tools for an existing page. It stops short of naming the retrieval alternatives (e.g. get_keywords) it should be preferred over, so it is clear context without full when-not guidance.

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