get_keyword_detail

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, destructive actions, rate limits, or data coverage. The phrase 'Daily time series' is vague and does not explain what kind of data is returned or how it behaves.

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 concise at 4 words. It front-loads the core idea. However, it lacks structure and any additional critical information. It earns its place but could be expanded without losing conciseness.

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?

Given the complexity (no parameters, no output schema, no annotations), the description is insufficient. It does not explain the output format, date range, metric types, or how the keyword is specified. For a tool returning time series data, this is a significant gap.

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 input schema has no defined parameters (only additionalProperties: true), so schema description coverage is 100%. The description adds no parameter-level meaning because there are none. However, the description fails to explain how the tool identifies which query to retrieve data for—likely from context or previous selection—which is critical for usage. Baseline 3 is appropriate as schema carries the load but leaves ambiguity.

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?

Description states 'Daily time series for a single query.' This implies retrieval of time-series data for one keyword query. The verb is implied by the tool name 'get', and the resource is clearly 'time series' for a single query. It is not a tautology and somewhat distinguishes from siblings like 'get_top_keywords' which returns multiple keywords. However, it could be more explicit (e.g., 'Retrieves daily time series metrics for a specified keyword').

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 use this tool versus alternatives. There are sibling tools like 'get_page_detail', 'get_top_keywords', and 'list_keywords_for_page' that might overlap. The description provides no context for selection or exclusions.

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