Domain Ads by Domain

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

With no annotations, the description carries the full burden for behavioral disclosure. It implies read-only behavior via 'Fetch' but does not mention pagination, date-range handling, dependence on the source country code, or what the response contains. Not misleading, but very thin.

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 short and has no filler words; every token contributes. However, the brevity sacrifices valuable context, making it effectively minimal rather than well-structured.

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 no annotations, no output schema, and a moderate six-parameter schema, the description is too sparse to be contextually complete. It fails to explain what 'domain ads' are, the role of source and date range, or how this tool differs from domainAdsByKeyword, all of which matter for correct selection and invocation.

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 100% parameter description coverage, so the schema already documents all parameter meanings. The description's 'by domain' merely maps to the domain parameter and adds no additional semantic detail beyond the schema.

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 states a specific action ('Fetch') and resource ('domain ads') scoped by domain, with the endpoint reference adding a small amount of clarity. It is not a tautology because it adds the verb 'Fetch', but it largely mirrors the tool name and does not elaborate on what 'domain ads' means.

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 is provided on when to use this tool versus the closely related domainAdsByKeyword or other siblings. There are no exclusions, prerequisites, or specific use cases mentioned, so an agent has to infer suitability entirely from the name and schema.

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