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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful caveats beyond those annotations, such as "estimated traffic is not measured visits," "One fixed Live POST, no pagination," and explicit handling of unknown/missing values, but phrases like "Execution and publication remain unapproved" are unclear rather than informative.

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 short and front-loaded, but it reads as a set of disjoint, jargon-heavy statements. Sentences like "Execution and publication remain unapproved" and "Successful completed results remain available in owner call history" add words without clarifying how to invoke the tool.

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 five-parameter read tool with no output schema, the description is incomplete: it neither explains the inputs nor describes the returned historical profile data. It also provides no usage context relative to the many sibling keyword-history tools.

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% and the description says nothing about the five parameters (keywords, fromMonth, toMonth, market, language). The only parameter-adjacent sentence, about seven-day freshness rules, does not explain any input's meaning or format.

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 first sentence simply restates the title ("Keyword Historical Profile Snapshots") and never states a clear verb or what specific historical keyword facts are returned. "Bounded Google database facts" is too vague to distinguish this from sibling tools such as nexscope_seo_keyword_interest_history or nexscope_amazon_keyword_search_history.

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 when-to-use guidance, no exclusions, and does not name any alternative sibling tool. An agent has to infer usage entirely from the name and title.

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