21st_magic_component_refiner

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does mention that the tool returns a redesigned version and implementation instructions, which gives some output behavior. However, it does not disclose whether the tool modifies the file (write), requires specific permissions, or has any side effects. This ambiguity could mislead the agent about the tool's mutability.

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 two sentences, front-loaded with an explicit usage directive, and every sentence earns its place. It is concise without redundancy, efficiently conveying purpose, usage, and output.

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?

The description covers the tool's purpose, when to use it, and what it returns (redesigned version + instructions), which is essential for a tool with no output schema. It leverages the schema's rich parameter descriptions. However, the lack of side-effect transparency and absence of annotations leave a small gap in complete understanding of the tool's behavior.

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%, and each parameter has a detailed description, especially 'context' which explains what to extract and what to do if nothing specific is mentioned. Since the schema fully documents parameters, the description adds no extra semantics, but the schema already provides sufficient meaning.

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 states a specific verb+resource: 'improves UI of components and returns redesigned version of the component and instructions on how to implement it.' It distinguishes from siblings by specifying it is for refining existing components (not building) and excludes big pages, which aligns with the tool name and differentiates it from 21st_magic_component_builder.

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?

It clearly says when to use: when the user requests to re-design/refine/improve a current UI component with /ui or /21 commands, or when context is about improving/refining a React component/molecule. It also excludes big pages. However, it does not explicitly name alternatives (e.g., 'use builder for new components'), so it lacks full explicit alternative guidance.

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