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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety behavior is covered. The description adds some transparency by naming the returned metrics, but it does not clarify ordering, date handling, row limits, or response shape.

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?

A single sentence that is front-loaded with the core action and resource. No filler or repetition; it is appropriately sized for its role.

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 gives a minimal sense of what is returned but omits sorting behavior, date-range semantics, and the meaning of 'top'. It is adequate for a simple read-only retrieval but leaves several operational details unspecified.

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%; site_url is documented but start_date, end_date, type, and row_limit are not. The description mainly restates 'property' and mentions output metrics, adding little semantic meaning for the parameters beyond what the schema already provides.

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 and resource: gets Google Search Console pages for a property. It also lists the output metrics (clicks, impressions, CTR, average position), which distinguishes it from siblings like get_gsc_top_queries or get_gsc_page_queries.

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 purpose implies use when page-level GSC performance is needed, but the description does not explicitly say when to choose this over alternatives such as get_gsc_top_queries or query_gsc_search_analytics. Context is clear but routing guidance is left to inference.

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