track_events

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

The description explicitly states 'Read-only' and 'POST-body params are flagged, not decoded', which adds behavioral detail beyond the annotations. It also indicates output format (one line per event). No contradiction with annotations (readOnlyHint=true, etc.) and the additional limitation on POST-body is valuable.

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 concise, two sentences, front-loaded with the main purpose and the tracker list, and includes the read-only note and POST-body limitation. Every sentence adds value with no 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 specialized decoding tool, the description explains what it does, which sources it covers, output format (one line per event), and read-only nature. It lacks a detailed output schema description, but the given summary is sufficient for an agent to understand the expected result. Given the tool's complexity, this is nearly complete.

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 fully documents all three parameters (clear, tab_id, wait_ms). The tool description does not add any parameter-specific semantics beyond what the schema provides, so the baseline of 3 applies.

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: decoding tracking beacons (GA4, Meta Pixel, etc.) from the browser network log, with output as one line per event. It is specific about the resource and lists the major tracker types, and it distinguishes itself from generic network tools like monitor_network.

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 gives clear context: it is for tracking beacons specifically, not all network traffic. However, it does not explicitly mention when not to use it or name alternatives, so it lacks explicit exclusions but provides enough context for an agent to infer appropriate use.

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