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

Annotations already establish readOnlyHint and non-destructive behavior. The description goes beyond annotations by disclosing exactly what the tool returns ('page URL, total clicks, impressions, avg CTR, avg position'), which is important because no output schema exists. No hidden side effects or state changes are implied.

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: what it does, what it returns, when to use it. The description is front-loaded and each sentence earns its place with no fluff or repetition.

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?

For a read-only, non-destructive tool with a fully documented schema, the description is nearly complete. It states the data source, output fields, and common use cases. It could add an example or note about the default date range, but the schema already covers those defaults.

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 the input schema already documents all parameters including defaults and constraints. The description adds no extra parameter context, such as how search filtering or sort behavior works, but it does not need to compensate because the schema is thorough.

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 names a specific verb ('Get'), resource ('top performing pages'), and data source ('Search Console data'), and lists the returned metrics. It is clear and distinct from likely siblings like get_top_queries, though it does not explicitly call out that sibling for differentiation.

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 phrase 'Use for content performance analysis, finding underperforming pages, identifying top content' gives concrete usage context. It does not mention exclusions or when to prefer a sibling tool, but the intended scenarios are clear enough.

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