browserslist_compatibility_check

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

With no annotations, the description carries the behavioral burden. It clearly indicates the tool reads and analyzes browserslist configuration rather than modifying anything, which is useful. However, it does not describe what happens if no config is found, how sources take precedence, or what the result format looks like, so some behavioral ambiguity remains.

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 contain no filler, and the primary action is front-loaded in the first sentence. The second sentence expands only with the concrete configuration sources, all of which are relevant to invoking the tool correctly.

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?

The description covers what the tool does and which configuration sources it reads, which is sufficient to invoke it. However, there is no output schema and the description does not describe the return value, failure behavior, or how to choose between this and caniuse_feature, leaving some uncertainty about what to expect after the call.

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 the baseline is 3. The schema already documents feature, configPath, projectPath, and browserslistQuery with examples; the description adds no parameter-specific meaning beyond restating the config-source options, so it neither improves nor undermines the already complete schema documentation.

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 opens with a specific verb and resource: 'Check web feature compatibility against your browserslist configuration.' It names the concrete config sources (query, .browserslistrc, package.json browserslist field), and this configuration-scoped behavior clearly distinguishes it from the broader caniuse_feature sibling without needing to inspect schemas.

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?

The description makes the usage context clear: use this tool when you want to evaluate a feature against the browsers defined by a browserslist source. It does not explicitly name caniuse_feature as the alternative for general compatibility lookups, so there is no when-not-to-use guidance, but the intended scenario is well implied.

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