Performance Page Load Analyze

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

With no annotations, the description carries the full behavioral burden and does not meet it. It does not say the tool fetches the live URL (a network/state-touching operation), whether it requires a running site or admin auth, or that the request is repeated (the runs parameter implies multiple loads with no explanation).

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 short sentence with nothing wasted and the purpose front-loaded. The brevity is not really conciseness though; it reflects under-specification for a tool with non-obvious semantics.

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 described, but the description omits what the analysis covers, whether it runs repeatedly, and any environment prerequisites. For a live-page diagnostic with 0% parameter documentation, this is incomplete.

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 0%, so the description must compensate and does not. The url parameter is loosely implied by 'page load,' but the runs parameter (default 3) and its averaging/variance semantics are never explained, leaving half the parameters undocumented.

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 states a verb (Analyze) and a resource (page load performance), which is more informative than the bare tool name. However, it is essentially the title reworded, adding no specificity about what is measured (LCP, TTFB, Core Web Vitals, asset timing) and no differentiation from the many performance_* siblings.

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?

There is no guidance on when to reach for this tool versus performance_query_log, performance_cache_stats, or the accessibility scan tools. No prerequisites (e.g., a reachable live site) or exclusions are stated, leaving the agent to infer usage entirely.

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