pilot_block

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

Discloses that blocked requests are aborted before reaching the network, resulting in faster loads and smaller snapshots. Also notes that invalid patterns are silently ignored. With no annotations, the description fully handles transparency.

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?

Well-structured into a summary, usage advice, parameter details, return info, and error note. Every sentence is informative with no wasted words.

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?

Covers all aspects: purpose, parameters, behavior, return values, and errors. With no output schema, the description provides complete context for the agent to use the 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?

Adds meaning beyond the schema: provides examples for patterns, explains the 'ads' preset blocks ~20 networks, and clarifies the clear mode. Also describes return values for add and clear modes, which is not in the 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?

Clearly states the tool blocks network requests to speed up page loads and reduce token noise. Uses specific verb 'block' and resource 'network requests'. Differentiates from siblings by focusing on ad/tracker blocking.

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?

Explicitly says when to use: when user wants to block ads, trackers, analytics scripts. Mentions the 'ads' preset for a common use case. Does not mention when not to use or alternatives among siblings, but provides clear context.

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