Get Ads Stats

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

No annotations are provided, so the description must disclose all behavioral traits. It merely states the output (total number of top/bottom ads by day) but omits critical details such as authentication needs, rate limits, read-only nature, or return format. The agent cannot infer safety or side effects.

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 concise, consisting of two short sentences with no unnecessary words. It front-loads the project ID requirement and then states the purpose. However, it could be more structured by briefly listing the core parameters.

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 5 parameters and no output schema, the description is too brief. It fails to explain what 'top' and 'bottom' advertisements mean, how date filtering works, or the effect of keyword/site engine filters. The agent has insufficient context to use the tool effectively.

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 coverage is 100%, so baseline is 3. The description adds no parameter-specific details beyond what the schema already provides. The relation between 'project ID' and 'site_id' is unclear, and no additional constraints or formats are explained.

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 specifies the tool's action: it retrieves the total number of top and bottom advertisements aggregated by day. The verb 'Get' and resource 'ads stats' are explicit, and the scope ('by day') distinguishes it from other PROJECT_ tools like 'getKeywordStats' or 'getSummary'.

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 states a requirement for a project ID but uses 'site_id' in the schema, creating inconsistency. It provides no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites beyond the vague project ID requirement.

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