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

No annotations are provided, so the description must carry the full burden. It does not disclose any behavioral traits beyond the core function—no mention of read-only nature, permissions, rate limits, or effects. This leaves the agent uninformed about important constraints.

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 two sentences with no wasted words: first sentence defines the function, second provides usage guidance. It is front-loaded and efficiently communicates the core purpose and context.

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 hints at output fields (clicks, impressions, positions) but does not explain return format, pagination, or sorting. Since there is no output schema, the description should be more explicit. The schema covers all parameters, so the description is adequate but not fully complete.

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 baseline is 3. The description adds no additional parameter-level information beyond what the schema's property descriptions provide. No parameter details are mentioned in the description.

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 clearly states it gets per-page search performance from Google Search Console, specifying metrics (clicks, impressions, positions). It uses a specific verb 'Get' and resource 'per-page search performance', distinguishing it from siblings like 'get_search_performance' which likely operates at a higher level.

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 gives clear usage context: 'Use when analyzing content performance or identifying top-performing pages.' However, it does not provide when-not-to-use or mention alternative tools, which would be helpful given the large sibling list.

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