refactor_component

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

With no annotations, the description must disclose behavioral traits. It only says 'provide expert-level refactoring suggestions and implementations' without stating important aspects: whether it returns code diffs or explanations, whether it modifies files, if it requires authentication, or any side effects. This is insufficient for an AI agent to anticipate behavior.

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, making it concise. However, it is too vague to be fully effective; a more specific sentence of similar length could be more informative. It is not overly long, but it sacrifices completeness for brevity.

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 tool's complexity (component refactoring with multiple types), the description lacks details about what the agent will receive as output (since no output schema exists), how the refactoring is presented, or any prerequisites. The 4-parameter schema is fully described, but the description does not complement it with higher-level context.

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 each parameter is already documented by the schema. The description adds no further meaning or context about the parameters (e.g., valid values for 'target_rn_version' or what 'include_tests' entails). Baseline 3 is appropriate as schema does the heavy lifting.

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 the tool provides 'expert-level refactoring suggestions and implementations', which is a clear verb+resource goal. However, it does not differentiate from sibling tools like 'analyze_component' or 'remediate_code', and the scope (component-level) is only implied by the name, not restated in the description.

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 when to prefer 'refactor_component' over 'remediate_code' or 'analyze_component'. There are no usage conditions, prerequisites, or exclusions mentioned.

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