refine_component

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

With no annotations, the description carries the full burden. It discloses that the tool applies fixes and upgrades, and mentions 'Iteratively improve', implying multiple rounds. However, it does not explain the output format, whether changes are saved directly, or any side effects like code overwriting. The behavioral disclosure is adequate but not thorough.

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?

Three sentences, each adding value: first sentence states purpose, second lists capabilities, third asserts framework support. No redundancy, front-loaded purpose. Ideal length for quick understanding.

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?

Given no output schema and no annotations, the description covers the tool's purpose and capabilities well. Missing details: return value description, constraints (e.g., code size limits), and clarification of 'iteratively' (whether multiple calls are needed). Still, it's largely complete for a refinement tool with well-named parameters.

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%, so baseline is 3. The description adds limited extra meaning beyond the schema: it groups feedback examples and mentions 'supports all frameworks' which aligns with the framework enum. It does not offer deep parameter semantics or usage tips beyond what the schema already 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?

Description clearly states 'Iteratively improve an existing component' using a strong verb and specific resource. It lists concrete improvement types (accessibility, dark mode, responsive, library upgrades) and notes framework support, differentiating from sibling tools like generate_ui_component which create new components.

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?

Description provides examples of when to use (feedback like 'make it more responsive') and states it supports all frameworks. However, it does not explicitly mention when not to use this tool or suggest alternatives like generate_ui_component for creating new components from scratch.

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