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

With only readOnlyHint=false and openWorldHint=true in annotations, the description adds useful caveats: nullable fields preserve missing evidence, provider observations and estimates are not actual account performance, and no fallback calls are made. It does not contradict the annotations, though it still omits details such as whether the search can incur provider-side effects despite being a 'search' tool.

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?

Four short sentences, front-loaded with the core output and followed by caveats. It is compact and has little waste, though the first sentence is terse enough to be ambiguous.

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 simple two-parameter search tool with no output schema, the description gives some output context and important evidence caveats. However, it omits core invocation guidance for query and limit, so an agent still has to infer how to use the parameters correctly.

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 two parameters with 0% description coverage, and the description does not explain what query should contain or how limit affects results. The parameter names are mostly self-explanatory, but the description adds essentially no semantic value beyond the schema.

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 indicates that this tool returns advertiser directory matches with approximate ad counts, so the resource is identifiable. However, the phrasing lacks a clear verb and does not distinguish it from nearby SEO ad/search tools such as nexscope_seo_ad_transparency_search or nexscope_seo_ad_audience_estimate.

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?

It gives no explicit when-to-use guidance, no prerequisites, and no comparison to sibling tools. The note 'No additional calls or fallback' is a behavioral constraint, not usage guidance for choosing this tool over alternatives.

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