convert_html_to_uxml

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

The description says it 'returns conversion patterns and best practices', which conflicts with the tool name's implication of performing a conversion. This ambiguity is misleading; the actual behavior (whether it outputs converted UXML or just patterns) is not disclosed. No annotations exist to mitigate this.

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 only two sentences, concise and front-loaded. However, the phrasing could be more precise without adding length.

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 tool with no output schema, the description covers the purpose but lacks details on output format, limitations, or when it might not work. It is adequate but not thorough.

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 coverage is 100%, so the parameter is already well-described in the schema. The description adds only general context about guidance and examples, not additional semantic detail beyond what the schema provides.

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 the tool converts HTML to UXML, but adds ambiguity by mentioning 'guidance and examples' and 'conversion patterns', which may imply it is a reference rather than an actual converter. It distinguishes from sibling tools that fetch code examples or references.

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 explicit guidance on when to use this tool versus alternatives. Sibling tools suggest possible overlaps (e.g., getting code examples), but no when-not-to-use or prerequisite conditions are provided.

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