searchatlas_ppc

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions three functional areas but doesn't describe how the tool behaves—e.g., whether it executes actions or just analyzes, what permissions are needed, if it modifies live campaigns, rate limits, or output format. The description is too high-level to guide an agent on behavioral expectations.

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, efficient sentence that front-loads the key domain and functions without unnecessary words. However, it could be more structured by separating the three functions for clarity, and it lacks any follow-up context that might be useful for an agent.

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 complexity implied by managing P campaigns (which often involve mutations and analysis), no annotations, no output schema, and four parameters, the description is incomplete. It doesn't address how the tool integrates with the broader system (e.g., via playbooks or projects mentioned in parameters), what results to expect, or safety considerations for a potentially destructive domain like ad management.

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 100%, so the schema fully documents all four parameters. The description adds no parameter-specific information beyond implying the tool handles PPC-related messages. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though the description doesn't compensate with additional context like example messages or parameter interactions.

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's purpose as 'PPC / Google Ads management — campaign creation, bid strategy, and performance analysis', which specifies the domain (PPC/Google Ads) and three key functions. It distinguishes from most siblings (e.g., content, keywords, SEO tools) by focusing on paid advertising, though it doesn't explicitly differentiate from all possible alternatives within the same domain.

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 provides no guidance on when to use this tool versus alternatives. It mentions three functions but doesn't specify contexts for campaign creation vs. bid strategy vs. performance analysis, nor does it reference sibling tools like searchatlas_run_playbook that might overlap. No exclusions or prerequisites are stated.

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