rush_slop

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

With no annotations, the description carries the full disclosure burden. It adds one useful behavioral detail: missing sloppylint produces status='skipped' when no JS/TS fallback applies. It does not state whether the operation is read-only, whether files are modified, or what other statuses or side effects are possible.

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 one dense sentence with the core purpose front-loaded and the edge case appended after the semicolon. It is concise and scannable, though the unexplained jargon and compact phrasing reduce readability slightly.

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 one-parameter tool with an output schema, the description is mostly sufficient to invoke it: it identifies the target path and exposes a key fallback behavior. However, it leaves ambiguity about what counts as slop or deterministic noise and does not explain when the JS/TS fallback applies, especially without annotation 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 0%, so the description needs to compensate. The '<path>' placeholder only repeats the schema's 'Path' parameter and does not clarify whether path should be a file, directory, glob, or what constraints exist. No additional semantic meaning is provided.

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 concrete action ('Detect') and a specific resource: Python AI slop and JS/TS noise at a path. This helps distinguish it from generic siblings like rush_lint or rush_review. The jargon phrases like 'deterministic JS/TS noise' and 'sloppylint' slightly obscure the precise meaning.

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 intended use case is implied: call it to detect slop or noise in Python or JS/TS code. However, there is no explicit guidance on when to choose rush_slop over alternatives, nor any mention of when not to use it.

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