Find conflicting Tailwind classes

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavioral context: overrides happen 'silently' and the tie-break follows Tailwind's own class order. It omits anything about output shape or scale limits, but it goes beyond what the annotations state.

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, no filler, with the outcome (which class wins, which is overridden) front-loaded and the tie-break rule stated immediately after. Every sentence earns its place.

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?

There is no output schema, so the description has to convey the return value, and it does so at a high level (winner plus overridden classes) without describing the result's structure or field names. For a two-parameter, read-only tool this is nearly complete, with only the response shape left unspecified.

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% -- both 'project' (path semantics, default working directory) and 'candidates' (with an example list) are fully documented in the schema. The description adds no parameter-level detail, so the baseline 3 applies.

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?

States a specific verb and resource: it reports which conflicting Tailwind class wins and which are silently overridden. That is precise enough to separate it from siblings like tailwind_validate (rule-checking) or tailwind_canonicalize (rewriting class order).

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?

Usage is only implied by the scenario ('when several set the same CSS property'); there is no explicit when-to-use statement, no exclusions, and no named alternative among the eight sibling tools. Adequate but leaves routing to inference.

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