get_competitor_patterns

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

No annotations are provided, so the description carries the burden. It discloses that it returns counts only (no predictions) and requires at least one deconstructed ad. However, it doesn't mention whether this is a read-only operation, potential rate limits, or what happens if no deconstructed ads exist (error vs. empty result).

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?

Two sentences, front-loaded with the core purpose, includes concrete examples, and ends with a clear prerequisite. Zero waste.

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?

For a single-parameter tool with 100% schema coverage and no output schema, the description is quite complete. It explains what the tool does, what it returns (counts, not predictions), and the prerequisite. The only gap is edge-case behavior (no deconstructed ads), but that's minor given the prerequisite is stated.

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% (competitor_id is described as 'The BrandCompetitor id (from the brands the user watches)'). The description adds context that the competitor must have deconstructed ads, but doesn't add much beyond the schema. Baseline 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 aggregates structural patterns across all of a competitor's deconstructed ads, with specific examples (problem-solution hook, editing rhythm, first-scene shot). It distinguishes from siblings by emphasizing 'aggregated patterns' vs. individual ad retrieval (get_ad_deconstruction, search_competitor_ads).

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: when you need aggregated structural patterns across a competitor's ads, not individual ads. It notes the prerequisite of at least one deconstructed ad. However, it doesn't explicitly contrast with alternatives like get_competitor_timeline or get_craft_playbook, though the 'counts only, no predictions' clarifies scope.

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