browser_sec_stop_csp_monitoring

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

The description discloses that it stops monitoring and clears violations, which is the key behavioral trait. However, with no annotations, it doesn't elaborate on whether the clearing is irreversible or if it affects other state. It's minimally adequate.

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?

The description is a single clear sentence with an optional reference. No wasted words; the action is front-loaded. It is as concise as possible for the complexity.

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 zero parameters and no output schema, the description is mostly complete, but it lacks context about what 'clear violations' means (e.g., are violations permanently lost?) and whether monitoring must be active. The reference to browser_docs partly compensates. It is adequate but not thorough.

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?

There are no parameters, so the description does not need to add parameter meaning. The schema coverage is 100%, and the description does not mislead. A baseline of 4 is appropriate given the absence of parameters.

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 explicitly states 'Stop CSP monitoring and clear violations', which clearly identifies the action (stop) and the resource (CSP monitoring) and distinguishes from siblings like browser_sec_start_csp_monitoring and browser_sec_get_csp_violations.

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?

No explicit guidance on when to use versus alternatives. It references 'see browser_docs', but does not state prerequisites (e.g., must have started monitoring first) or when not to use. This leaves the agent to infer usage context.

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