checkBrowserCompatibility

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

With no annotations provided, the description alone must disclose behavior. It only states 'check browser compatibility issues,' which implies a read-only operation but does not confirm it, nor does it describe what the output looks like, whether it makes network calls, handles errors, or has side effects. The agent is left without any behavioral expectations beyond the vague verb 'check.'

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 concise in length (one sentence) and front-loads the core action, but it is so minimal that it borders on under-specification rather than effective conciseness. No extraneous words, but also no meaningful content beyond a restatement of the name. Structure is acceptable but lacks substance.

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 the absence of an output schema and annotations, the description must explain return values and behavior, but it does not. It also omits what 'compatibility issues' means and how the optional userAgent parameter affects results. The tool likely works on a list of features, but the description gives no clue about expected output or edge cases, making it incomplete for an agent to call 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?

The schema covers both parameters (features and optional userAgent) with descriptions, so the baseline is 3. The tool description adds no additional meaning or context about these parameters—it doesn't explain how the userAgent affects results or what kinds of features are expected. It neither enhances nor contradicts the schema, so a 3 is appropriate.

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 states the verb 'check' and the resource 'browser compatibility issues,' which gives a general sense of the tool's purpose. However, it is vague about what specific aspects of compatibility are assessed (e.g., CSS features, APIs, specific browsers) and does not differentiate it from sibling tools. It is not a tautology but lacks specificity.

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?

There is no guidance on when to use this tool versus alternatives like analyzeConsoleErrors or testMantisEvent. No context is provided about typical scenarios, prerequisites, or when another tool would be more appropriate. The description does not help an agent decide between this and any sibling tool.

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