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

Annotations already state readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful filter semantics, notably that start_date and key/country matching are substring-based and that clicks_only means clicks > 0. It does not describe pagination behavior or result ordering.

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 description is a single tightly written sentence with the primary action front-loaded and the optional filters following efficiently. Every clause adds filtering information without waste.

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?

The description covers the main filter behavior, which is useful given zero schema description coverage. Because annotations cover safety and there is no output schema, it does not need to explain return fields, but it should still clarify pagination parameters and how this raw-row lister relates to the many gservice_query analytical siblings.

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 0%, so the description must carry parameter meaning; it explains website_id/website_uuid, start_date substring, key_query/country_query substring, and clicks_only. However, it omits the purpose and defaults of the page and per_page parameters, leaving two of eight parameters undocumented.

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 gives a specific verb and resource: "List gservice_query rows," and enumerates the available filters. It does not explicitly distinguish this raw-row listing from analytical siblings such as gservice_query_summary, gservice_query_breakdown, or gservice_query_daily.

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 description implies usage by listing optional filters, but it gives no explicit guidance on when to choose this tool versus gservice_query_summary, gservice_query_daily, gservice_query_grouped, or gservice_query_insights. There are no exclusions or alternatives named.

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