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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, open-world behavior, so the safety profile is covered. The description adds the non-obvious gating condition that monitoring must be enabled first, which prevents calls that would otherwise return empty data. It does not mention latency, caching, or empty-result behavior when monitoring is off.

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, both earning their place: the first front-loads what is measured, the second front-loads the blocker. No filler, no restatement of the tool name.

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?

With an output schema present, the description need not explain return values, and both parameters are schema-documented, so an agent has enough to call it correctly. The only gap is lack of explicit routing versus the analytics and bandwidth siblings, which matters given a 24-tool sibling set.

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%: site_name and the range enum are already fully documented in the schema. The description's mention of a "time-series chart" loosely implies the range parameter affects windowing, but adds no format or default guidance beyond what the schema provides. Baseline 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?

States a specific verb and resource ("Live HTTP traffic for a site") and enumerates the returned metrics (status-code breakdown, latency avg/p95, bandwidth, top error URLs, time series), which is far more concrete than the title. It does not explicitly distinguish itself from siblings like get_site_analytics or get_site_bandwidth, so an agent must infer the boundary.

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?

Gives a clear precondition for use—traffic monitoring must be enabled—and names the enabling tool in parentheses, which is genuinely actionable. It stops short of stating when to prefer this over get_site_analytics or get_site_bandwidth, so the alternative-selection guidance is incomplete.

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