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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no return format, no pagination or limit behavior despite a 'limit' param, and no note on what 'issues' means. It neither contradicts nor enriches the structured data.

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?

It is a single compact fragment with no wasted words, so it passes on brevity. However it is under-specified rather than appropriately sized for a 17-parameter tool, leaving no front-loaded context to orient the agent.

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?

An output schema exists, so return values need not be explained. But with 17 undocumented optional parameters and no usage guidance, the description falls well short of what an agent needs to invoke this tool correctly; only the read-only annotations carry any weight.

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?

The schema has 17 parameters at 0% description coverage, and the description mentions none of them. Date filters (days, date_from, date_to, range_preset), account identifiers (client_id, user_id, site_url, property_name), and controls like limit/sort_by are entirely undocumented, so an agent has no basis for populating them.

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 fragment names a specific resource ('on-page SEO metadata issues') but supplies no verb, so it's unclear whether the tool retrieves, lists, or analyzes them. The name search_get_page_metadata implies retrieval, and the resource is distinct from siblings like search_get_lighthouse or search_get_top_queries, but the description alone only implies the purpose.

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?

There is no when-to-use guidance, no statement of prerequisites, and no mention of the closely related search_get_lighthouse / search_get_metrics / search_get_top_queries alternatives. The single fragment provides no context for selecting this tool over its siblings.

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