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

With no annotations, the description carries the full behavioral burden. It implies a read-only retrieval operation, but gives no information about authentication needs, rate limits, response behavior, or how the required nested payload affects execution.

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 single sentence is front-loaded and not verbose, but it is under-specified for a tool with five operations and a large nested payload. Its brevity reflects missing information rather than efficient concision.

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?

The tool is complex, with a nested payload, multiple operation types, many optional parameters, and no annotations. The description does not cover any of that complexity or tell the agent how to invoke it correctly; only the output schema is pre-provided.

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% for the top-level parameter, and the description adds no meaning beyond 'data.' It does not mention the required payload object, the operation enum, filters, pagination, or any other parameter constraints.

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 verb ('Retrieve') and a broad resource ('search advertising and audience demand data'), but the resource is vague and overlaps with many siblings such as keyword-data, market-data, and competitor-data. It does not identify which operation or dataset is being accessed.

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 guidance on when to use this tool versus alternatives, and it names no sibling tools or conditions. It provides only a generic purpose statement.

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