lookalike_signal_generator

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

With no annotations, the description carries the full burden. It adds a useful behavioral note: 'generates criteria, not data', which clarifies the output type. However, it does not disclose other behaviors such as output format, any side effects, or whether it makes external calls. This is a minimal but meaningful disclosure.

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 a single sentence that is front-loaded with the main action and scope. It is concise, with no wasted words, and directly communicates the tool's purpose.

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 description is sufficient for a generation tool given the schema covers all inputs. However, without an output schema or more details on the structure of generated criteria, an agent may be uncertain about how to use the results. The note 'generates criteria, not data' partially addresses this, but more context on the output format would improve completeness.

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 schema provides 100% coverage of parameter descriptions, so the description does not need to add parameter details. It adds no extra semantics beyond the schema, so the baseline of 3 is appropriate.

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 a specific action: 'Generate platform-specific targeting criteria and search queries' with an explicit resource. It also distinguishes itself by noting '(generates criteria, not data)', which separates it from data retrieval tools. Among siblings which are all analysis tools, this stands out as a generation tool.

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 the sibling analysis tools is provided. There is no mention of prerequisites, context, or exclusions. The only hint is that it generates criteria, but no explicit statement of appropriate usage scenarios.

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