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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it fails entirely. It does not state whether the operation is read-only, what data it returns, how far back history goes, whether pagination applies, or what happens for an invalid advertiserId.

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 extremely sparse and reads as a title label rather than a concise, purposeful description. It contains only the version prefix 'V1' and the tool name, which is under-specification rather than efficient brevity.

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?

Despite the tool being relatively simple with one parameter, the description is incomplete for practical invocation. It does not define the input semantics, output shape, or any behavioral expectations, leaving the agent with almost no contextual basis for a correct call.

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 0%, so the description must compensate for the advertiserId parameter but does not. The single parameter is not explained anywhere in the description; the name 'advertiserId' is helpful but comes from the schema, not the description, so no additional semantic value is added.

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 'V1 Ads Google Advertiser History' is essentially a restatement of the tool name and does not include a verb or clearly define the operation. It suggests an advertiser history resource but fails to specify whether the tool retrieves, lists, or searches history, and provides no differentiation from siblings like ads_google_advertiser.

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 no guidance about when to use this tool versus its siblings or what kind of history it covers. There is no mention of prerequisites, filtering, or exclusion conditions, leaving the agent without any decision-support for selecting this tool.

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