content_setting_set

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a mutation ('Set') but does not state side effects, whether an existing setting is overwritten, permission requirements, or failure behavior. This is a minimal disclosure with no detail beyond the action itself.

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, front-loaded sentence with no redundant phrasing. It states the action, scope, and mechanism efficiently. It is under-specified in other dimensions, but as far as conciseness goes, it wastes no 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?

For a tool with three required parameters, no annotations, and no output schema, the description is far too thin. An agent cannot determine the format of primaryPattern, the significance of each setting value, whether changes are reversible, or what the response looks like. This is inadequate for correct invocation.

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 0%, so the description needs to compensate for the parameters. It only hints at 'per-site' (primaryPattern) and 'content setting' (kind), but does not explain the 'setting' parameter or the meaning of its enum values. The enums in the schema are self-explanatory only to a degree, but the description adds little beyond what the property names already convey.

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 uses a specific verb ('Set') with a concrete resource ('per-site Chrome content setting') and mechanism ('extension API'). It clearly communicates the tool's core action, though it does not explicitly contrast with the sibling content_setting_get or other alternatives.

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 guidance is given about when to use this tool versus alternatives like content_setting_get. The description implies a write operation but does not mention when to prefer it, what prerequisites exist, or how it differs from related tools.

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