rtl_layout_matrix

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 describes what the tool does (converts code, flips icons, applies Form BiDi rules) but does not disclose side effects, whether it is read-only, output format, limitations, or required permissions. This is a significant gap for a conversion tool.

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 dense sentence that front-loads the main action and purpose. It includes all key features without excessive filler. The structure is acceptable, though the sentence is somewhat long and could be split for readability.

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?

With no output schema, the description should explain what the conversion returns or how output is structured, but it does not. It also leaves two parameters undocumented and provides no guidance on output format or usage examples. The lack of return-value documentation and vague parameter handling make the description incomplete.

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 50%, with targetFormat and primaryDirection having empty descriptions. The tool description does not compensate by explaining allowed values or meaning for these parameters. It adds some context for flipDirectionalIcons ('directional icon flip') but leaves the core parameters ambiguous, hindering correct invocation.

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 clearly states a specific action ('Converts') and a specific resource ('legacy physical CSS/Tailwind/Flutter component code') with a clear outcome ('modern bidirectional (RTL/LTR) logical components'). It also mentions distinctive features (directional icon flip, Form BiDi rules) that separate it from audit or analysis sibling tools.

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 implies when to use the tool (when you have legacy physical component code to convert to bidirectional logical components) but does not explicitly mention alternatives or when not to use it. No clear exclusionary guidance is provided, so usage is inferred rather than explicitly stated.

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