get_competitor_timeline

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

With no annotations, the description carries the behavioral burden. It discloses ordering (newest first), includes lifespans, archived media, and emphasizes the observed_* vs platform_* field separation, which is a key behavioral trait. It also clarifies 'Facts only, no predictions.' It does not mention error handling or authentication, but for a read-like tool this is acceptable.

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 dense but each clause adds unique value: ordering, lifespans, archived media, observed/platform distinction, asset_id linking, and facts-only guarantee. It is structured with clear periods and front-loaded with the core purpose. No redundancy; each sentence earns its place.

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 output schema, the description adequately explains the return: chronological roster, lifespans, archived media, observed/platform fields, and asset_id for further lookup. It also mentions the continuous-monitoring nature. This covers the essential context an agent needs to interpret the output and decide next actions.

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 coverage is 100% with clear descriptions for all four parameters (limit, channel, active_only, competitor_id). The description does not add meaningful parameter-level details beyond what the schema provides, so the baseline score 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 the tool retrieves the chronological roster of one competitor's archived creatives, with specifics like newest-first ordering, lifespans, and archived media. It distinguishes from sibling tools like search_competitor_ads by focusing on a single competitor, and from get_my_competitor_ads by implying external brand tracking.

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 implies when to use: for a single competitor's complete archived history that cannot be reconstructed from other sources (continuous-monitoring archive). It also sets boundaries with 'Facts only, no predictions' and hints at using deconstruct_ad for deeper investigation. However, it does not explicitly name alternative tools for contrasting scenarios, so a slight deduction applies.

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