Get Render Blocking Resources

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

With no annotations provided, the description carries the full disclosure burden. It usefully clarifies the scope of the analysis (first-paint blocking, critical chains), but says nothing about authentication, rate limits, cost, or whether results are cached — behavioral traits an agent would want before invoking it.

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, front-loaded with the core purpose and then the specifics of what is identified. No filler and nothing redundant.

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 two-parameter analysis tool with no output schema and no annotations, the description tells the agent what the analysis is about but not what the response contains or how it differs operationally from sibling analyses. It is adequate but leaves the agent to infer the return shape and comparative value.

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 both 'url' and 'strategy' are already fully documented in the schema with an example and a default. The description adds no syntax, format, or defaulting nuance beyond the schema, 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 states a specific verb and resource: 'Get render-blocking resource analysis for a URL', and then enumerates what the analysis covers (CSS/JS blocking first paint, critical request chains, preconnect/preload opportunities). This distinguishes it from siblings like get_js_analysis and get_network_analysis, though it never names those alternatives directly.

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 only implied: an agent can infer it should call this when it wants render-blocking diagnostics for a page. There is no explicit when-to-use, when-not-to-use, or routing to sibling tools such as get_js_analysis or analyze_url, which is a clear gap in a nine-tool family.

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