traffic_health_check

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It only states the action 'compare' but does not disclose whether the tool is read-only, requires authentication, or what side-effects may occur. The absence of any behavioral notes (e.g., 'read-only', 'requires credentials') leaves significant ambiguity.

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, well-crafted sentence of 10 words. It is front-loaded with the main purpose ('Diagnose tracking issues') and includes the key method. Every word earns its place; there is no redundancy or fluff.

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?

Despite having 6 parameters (4 required) and no output schema, the description does not clarify the nature of the comparison output, the metrics returned, or any prerequisites. It fails to provide critical context for a tool that cross-references two external data sources, leaving users uncertain about what the result will be.

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 each parameter has a clear description in the schema (e.g., 'GSC Site URL', 'GA4 Property ID'). The tool description adds the context that these parameters are used to compare GSC and GA4 data, but this does not substantially enhance understanding beyond the schema. 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's purpose: 'Diagnose tracking issues by comparing GSC clicks vs GA4 organic sessions'. It uses a specific verb ('diagnose') and resource ('tracking issues'), and the method is well-defined. This effectively distinguishes it from sibling tools that focus on single-source analytics or other SEO tasks.

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. There is no mention of prerequisites, context for use, or comparison with sibling tools like analytics_* or seo_* tools. Users must infer usage from the purpose alone.

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