rush_simplify

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, but it does not explain whether the tool edits files in place, requires prior analysis, preserves behavior, or returns a diff/summary. 'Decompose' implies modification but leaves safety and side-effect expectations unclear.

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 front-loaded sentence with no filler or redundancy. It is concise, though it borders on under-specification by omitting usage and parameter details.

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?

For a tool with one required parameter, an optional threshold, no annotations, and many closely related sibling tools, this description is too thin. It conveys the basic purpose but leaves an agent without enough context to decide when to invoke it or how to set max_complexity.

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 0%, so the description must compensate for the undocumented parameters. It does not explain what 'file' refers to or how max_complexity is measured/used, though 'high-complexity' loosely implies the complexity threshold.

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 names a specific action ('decompose'), a clear target ('high-complexity functions'), and the intended outcome ('modular helpers'). This distinguishes it from sibling analysis tools like rush_complexity, since the focus is on transforming code structure rather than just measuring or reviewing it.

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 given about when to use this tool versus alternatives such as rush_complexity, rush_review, or rush_fix. The max_complexity parameter hints at a threshold condition, but the description never states it explicitly.

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