rtl_convert_tailwind

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

With no annotations and no output schema, the description carries the full behavioral burden. It discloses the direction of the mapping via examples but says nothing about what is returned, whether the operation is idempotent, whether it tolerates mixed class lists or unknown utilities, or how it fails on invalid input.

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?

One sentence, front-loaded with the verb and resource, followed by three compact examples that do more work than prose would. Nothing is wasted or buried.

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 single-parameter pure transformation the description is close to sufficient, but gaps remain: the input format for 'text' is only implied and the return value is never described despite there being no output schema. It is adequate to attempt a call but not to predict the result.

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 is a single required parameter 'text' with 0% schema description coverage, so the schema offers no meaning at all. The description's examples imply the parameter is a set of Tailwind utility classes, but it never states whether the input is a class string, a full HTML fragment, or file contents.

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 names a specific verb (Convert) and resource (Tailwind physical utilities to logical ones) and backs it with three concrete before/after examples, so the transformation is unambiguous. It stops short of explicitly differentiating itself from the sibling rtl_convert_css, but the Tailwind-specific examples make the boundary inferable.

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 statement of when to reach for this tool versus rtl_convert_css or rtl_audit_css, no prerequisites, and no note on what it does not handle (e.g. non-Tailwind CSS or arbitrary HTML). Usage is only implied by the examples, and a sibling with a near-identical name exists, so routing guidance is genuinely missing.

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