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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral value by disclosing exactly what the analysis computes (status distribution, slowest/largest, top hosts, timings), telling the agent this is a deterministic local parse-and-summarize rather than a fetch. It omits any note on large-file handling or truncation.

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?

A single front-loaded sentence with zero filler; the verb and resource lead, and the output enumeration follows efficiently. Nothing can be trimmed without losing informational 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?

An output schema exists, so return values need not be explained, and both parameters are fully documented at 100% coverage. With annotations carrying the safety profile, the description provides everything an agent needs to select and invoke this tool 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?

Schema description coverage is 100% – both 'har' and 'top' are fully documented in the schema, including minLength and 1-20 bounds for 'top'. The description's mention of 'slowest and largest requests, top hosts' echoes the purpose of the 'top' parameter but adds no syntax or format detail beyond the schema. 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 (parse/summarize) and resource (HAR HTTP Archive capture), then enumerates the exact outputs: request counts, status distribution, slowest/largest requests, top hosts, per-request timings. No sibling tool does HAR analysis, so it is unambiguously distinguishable from the rest of the catalog.

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?

Usage is implied by 'Parse a HAR (HTTP Archive) capture' – an agent knows this applies when it has HAR JSON to analyze. However, it names no alternatives or exclusions, and does not say how it relates to adjacent tools like check_http_headers, check_ssl, or fetch_page_markdown that also surface HTTP performance information.

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