analyze-analytics-platforms

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

With no annotations, the description carries full responsibility for disclosing side effects, auth needs, rate limits, or return behavior. It only says 'deep dive,' which implies a read-only analysis but provides no specifics about what is analyzed, how deep the inspection goes, or what the output contains. This falls short of useful behavioral disclosure.

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 sentence with no filler, but it is under-specified rather than efficiently concise. It front-loads the purpose but leaves out critical details, making it a hybrid of brevity and vagueness rather than a model of concise specification.

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 simplicity (only 2 params, no output schema) but the crowded sibling context, the description should explain what 'deep dive' yields, whether 'waitTime' affects depth, and how it differs from similar analytics tools. It does none of this, leaving the agent with insufficient contextual information to choose and invoke it correctly.

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?

The schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The description adds no extra meaning beyond the schema—it does not mention 'url' or 'waitTime' or how they affect the analysis. Thus, no value beyond structured data is provided.

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 identifies a specific resource (analytics platforms) with concrete examples (GA4, UA, Adobe Analytics) and uses 'deep dive' to imply a comprehensive analysis. It distinguishes from siblings like 'detect-ad-pixels' or 'identify-tag-managers' by focusing on analytics platforms rather than general marketing tech, though 'deep dive' lacks a precise operational verb.

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?

No guidance is provided on when to use this tool versus the many sibling tools (e.g., 'parse-analytics-beacons', 'scan-marketing-stack'). The description only states what it does, leaving the agent to infer potential alternatives without explicit exclusions or conditions.

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