gsc_build_traffic_drop_queue

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

The description correctly identifies the tool as 'read-only' and explains it compares current vs previous rows by dimension keys, returning stable JSON. However, with no annotations, it could disclose more about rate limits, data staleness, or behavior with missing data.

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?

Two efficient sentences: first states purpose, second adds methodology and output format. No redundant or extraneous information.

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 tool has 11 parameters (5 required), no schema description coverage, and no annotations, the description is insufficient to guide correct usage. The output schema exists but is not referenced, and parameter semantics are completely absent.

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?

With 0% schema description coverage, the description provides no explanation of parameters like site_url, date ranges, max_items, or dimensions. It adds no value beyond the raw schema, leaving the agent without guidance on how to properly set inputs.

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 clearly states the tool builds a 'read-only prioritized action queue for Search Analytics traffic drops' and mentions it uses two official query calls. However, it does not differentiate from sibling tools like compare_search_periods or other build_*_queue tools, leaving ambiguity about when to use this one.

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 vs. alternatives such as compare_search_periods. The description does not specify prerequisites, context, or when not to use it.

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