brand_analysis

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

No annotations are provided, so the description carries the full burden. It only states the tool 'Analyze[s] ... performance' without disclosing behavioral traits such as output format, read-only nature, authentication needs, or side effects. This is a significant gap for a tool with 9 parameters.

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, concise sentence front-loading the purpose. However, it is overly minimal for a tool with 9 parameters and no other documentation. It earns its place but lacks structure (e.g., bullet points) to improve readability or add needed detail.

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 lack of annotations, output schema, and the complexity of 9 parameters (6 required), the description is incomplete. It does not explain what the analysis returns, how results are presented, or any constraints (e.g., date formats, account prerequisites). The tool needs more context for reliable agent 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?

Schema description coverage is 100%, so the schema already documents each parameter. The description adds no extra meaning beyond the schema; it simply lists the data sources. Baseline of 3 is appropriate as the description does not compensate for any missing schema detail.

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 analyzes 'Brand vs Non-Brand performance' across three specified data sources (GSC, Bing, GA4), using a specific verb and resource. This distinguishes it from siblings like 'bing_brand_analysis' (Bing-only) and 'seo_brand_vs_nonbrand' (likely SEO-focused).

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 like 'seo_brand_vs_nonbrand' or 'bing_brand_analysis'. There is no mention of prerequisites, scenarios, or exclusions, leaving the agent to infer usage context.

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