generate_rtl_ltr_layout_matrix

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

With no annotations, the description carries the transparency burden. It does disclose the core conversion behavior and specific features like icon flip and Form BiDi rules, but it does not mention return behavior, side effects, error modes, or how the output is delivered. This is adequate but incomplete.

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 sentence, front-loaded with the action verb, and includes the key transformation details with no redundant filler. It is very efficient and easy to parse.

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 4-parameter tool with no output schema and no annotations, the description is too brief. It leaves targetFormat and primaryDirection undefined, gives no usage guidance, and does not state what the tool returns. The agent may not be able to invoke it 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 already documents componentSnippet and flipDirectionalIcons, and the description reinforces those. However targetFormat and primaryDirection have empty schema descriptions, and the description does not explain their meaning. At 50% schema description coverage, the description only partially compensates, so parameter semantics are weak.

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 uses a specific verb ('Converts') and identifies the resource ('legacy physical CSS/Tailwind/Flutter component code') with a clear output ('modern bidirectional logical components with directional icon flip and Form BiDi rules'). It clearly states the tool's purpose, though it does not explicitly differentiate it from sibling tools like rtl_layout_matrix.

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?

No guidance is provided on when to use this tool versus alternatives such as rtl_layout_matrix or design_tokens. The description does not mention prerequisites, exclusions, or appropriate use cases, leaving the agent without selection criteria.

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