reverse_engineer_component

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

Despite lacking annotations, the description fully discloses the tool's non-destructive nature and specifies what the tool returns (HTML, CSS, styling, states, accessibility). This covers key behavioral aspects beyond a simple 'analyze' label. No contradictions or hidden traits.

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?

Two sentences, front-loaded with the core purpose, followed by optional features and outputs. No redundant words or structure. Every sentence earns its place.

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 the lack of output schema, the description comprehensively lists all return categories (HTML, CSS, states, accessibility) and explains the optional region. It covers all necessary information for an agent to decide whether to invoke this tool.

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?

With 100% schema description coverage, the baseline is 3. The description adds minor semantic value by explaining the effect of the region parameter ('crop + zoom for focused analysis') and linking element_description to the component. This is adequate but not exceptional.

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's purpose: reverse-engineering a single component from a design. It distinguishes from sibling tools (e.g., analyze_design, analyze_layout) by specifying the output (HTML, CSS, states, accessibility) and the optional region cropping. The verb 'reverse-engineer' combined with 'component' is specific and unambiguous.

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 provides context on when to use the tool (for component analysis and optional region focus) but does not explicitly state when not to use it or direct users to sibling alternatives. However, the purpose is clear enough that an agent can infer usage boundaries.

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