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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds the data-source dependency and the returned measures (clicks, impressions, average place), but omits anything about empty-result behavior for unconnected sites or how large result sets behave.

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?

Three short sentences, front-loaded with the core resource and metrics before the prerequisite and the formatting note. No filler, though the final sentence about quoted queries is telegraphic enough to be slightly ambiguous.

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 the burden of describing returns and does name the three metrics; pagination is handled in the schema via limit/offset. The only meaningful gap is that it never explains what an empty answer looks like when the site is not connected to Search Console.

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 coverage is 100%, so all five parameters including the 'show' enum are already documented. The description restates the same modes ('by query, by page, or only those close to the top') without adding syntax or defaulting information beyond the schema. It does add one output-format note: queries appear under quotes.

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 resource and source: the Google searches a site's pages were shown for, from Search Console, with the metrics returned. It also flags the three shapes (by query, by page, near-top). It does not name or contrast with any sibling (mttr_near, mttr_traffic, mttr_search), so an agent must infer the boundary.

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?

The prerequisite is explicit and valuable: 'Only sites whose owner added mttr in Search Console have any' tells the agent when this tool will return nothing. However, there is no guidance on when to pick this over mttr_near or mttr_traffic, which overlap on the same subject matter.

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