Seed Demo Ad Portfolio

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

Description discloses that the tool creates data (consistent with readOnlyHint=false) and appends new portfolios each call (consistent with idempotentHint=false). It adds context beyond annotations by explaining the demo nature and safety of multiple calls.

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?

Extremely concise at two sentences. First sentence provides purpose and content; second sentence adds usage guidance and safety. No wasted words, information is front-loaded.

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 zero parameters, no output schema, and the tool's role as a demo data generator, the description fully covers what the tool does, what data it creates, and when to use it. AI agents have sufficient information to decide 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?

Tool has zero parameters, so description adds no parameter semantics beyond what's already known from the input schema. Baseline of 4 is appropriate since there is no need for parameter description.

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 creates a realistic cross-platform ad portfolio for trying AdOps without real data. It specifies exactly what is seeded (2 connections, 8 campaigns, 30 days metrics, anomaly alerts) and distinguishes it from sibling tool ad_csv_import for real data.

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?

Provides explicit when-to-use guidance: 'Use this to explore what AdOps can do, then switch to ad_csv_import with your real Google/Meta exports for production use.' Also notes it's safe to call multiple times (appends), giving clear usage boundaries.

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