browser_block_urls

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

No annotations provided, so description must compensate. It states requests are aborted, but lacks details on scope (per-session?), side effects, or whether it's persistent. Basic disclosure but missing depth.

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 with no wasted words. However, for a tool with 2 parameters and no schema descriptions, it is under-specified rather than optimally concise. Could include more detail without becoming verbose.

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?

Given 2 parameters, no schema descriptions, and an output schema (not shown), the description lacks guidance on pattern syntax, scope, and return values. Incomplete for effective tool usage.

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 coverage is 0%, so description must explain parameters. It only mentions patterns with examples, but no format details. session_id parameter is not explained. Minimal addition over schema.

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?

Description clearly states the verb 'Abort' and resource 'requests matching glob patterns'. Provides examples and use case, distinguishing it from sibling tools like browser_unblock_urls.

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?

Gives context for when to use: 'to save proxy bandwidth or strip trackers/images'. Does not explicitly state when not to use, but the sibling list includes the complementary unblock tool, implying the context.

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