web_traffic_summary

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

With no annotations provided, the description carries full burden. It clearly states the tool is read-only, summarizes logs, and auto-discovers log paths. This sufficiently discloses the main behavioral traits. No contradictions.

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?

Three concise sentences, each adding unique value: core function, distinction from sibling, and auto-discovery/read-only flag. No redundant or filler content.

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?

The tool has no output schema, but the description enumerates the expected return items (vhost volume, req/s, status mix, top IPs/URLs). Combined with full schema coverage on inputs, the description is sufficiently complete for a read-only analysis tool.

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 all parameters adequately. The description adds marginal context beyond the schema, such as auto-discovery on log_path omission, but does not significantly enhance parameter understanding.

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 verb 'Summarize' and the resource 'managed instance's OWN web access logs', and specifies the outputs (vhost volume, req/s, status mix, top IPs/URLs). It also distinguishes from the sibling tool 'cloudwatch_top_ips' by noting it reads on-box logs vs WAF logs.

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 explicitly mentions when to use this tool over an alternative ('cloudwatch_top_ips') by highlighting the difference in data source. It also notes auto-discovery of log path. However, it does not provide a comprehensive list of when not to use it, but the context is clear.

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