browser_block_resources

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

With no annotations provided, the description carries the full behavioral burden. It reveals nothing about scope (current tab vs. all tabs), persistence across navigations, whether blocking is reversible, or how it interacts with existing blocks — all critical for a filtering/mutation tool.

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 well-formed sentence that front-loads the action, lists the targets, and ends with the payoff. Every clause earns its place.

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 5-parameter, zero-required tool with no annotations and no output schema, the description covers what is blocked but omits scope and persistence details the agent needs to invoke it correctly. It is adequate but leaves meaningful gaps.

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 each parameter is already documented. The description restates the same categories (images, media, fonts, trackers) without adding format or default semantics 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 gives a clear verb ('Block') and enumerates the resource categories plus custom URLs, so the agent knows exactly what the tool affects. It does not, however, distinguish itself from the sibling browser_block_urls, which likely overlaps in function.

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?

It states the benefit (accelerated page load) but gives no explicit when-to-use, when-not-to-use, or prerequisite context, and never mentions the closely related browser_block_urls sibling. The agent must infer when this is preferable to that alternative.

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