remediate_component

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states 'Mutates the file on disk' and lists the AST transformations performed. It could add details about irreversibility or file backup, but the core mutation behavior is clearly disclosed.

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 cover action, target, specific transformations, threshold condition, and mutation warning. No redundant phrasing; every clause earns its place. Front-loaded with 'Automatically optimizes' for quick comprehension.

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 a clear action-oriented role, the description is complete for a mutation tool. It covers behavior, mutation, and input semantics via the schema and description. Minor gaps include error handling and rollback details, but these are not critical given the schema and sibling 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 coverage is 100%, so the baseline is 3. The description adds value by explaining the ROI threshold (1.5) that triggers React.memo and clarifies that unstable_props are wrapped in hooks, providing context beyond the individual property descriptions.

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 that the tool automatically optimizes a React component's AST with specific transformations (hoisting, useCallback/useMemo, React.memo). This distinguishes it from all sibling analysis tools, which focus on profiling and diagnosis rather than modification.

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 gives a condition for using the tool (ROI score above 1.5) but does not explicitly state when to use it instead of sibling tools like suggest_memoization or diagnose_hydration_and_suspense. It implies usage after profiling, but lacks explicit exclusions or alternative guidance.

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