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

Annotations already declare readOnlyHint/destructiveHint=false, so 'No writes or access grants' largely restates structured data. The one genuine addition is that restricted services demand fresh server-verified access and otherwise refuse, which discloses an auth/failure behavior not in the annotations.

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, front-loaded sentences with no filler; the read action leads and constraints follow. Slightly dense jargon ('bounded native') costs it the top score.

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 tool with no output schema and safety annotations, the description covers the access constraint but omits return-shape expectations and leaves the empty required 'body' parameter unaddressed. Adequate but with visible gaps.

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 only 33%, yet the description says nothing about any parameter. The required 'body' object is empty with additionalProperties=false, which is unexplained, and connection_context's purpose is left to the schema pattern alone.

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 ('Read') and resource ('benchmark_sources insight'), and the resource name cleanly separates it from the benchmark_dates/locations/metrics/products siblings. The qualifier 'bounded native' is jargon that adds little precision, but the core action is identifiable.

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?

No guidance on when to choose this tool over the sibling benchmark_* tools, nor when it is appropriate versus google_ads_insights_* tools. The 'restricted services require fresh server-verified access' line is a precondition, not usage routing.

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