rush_tdd

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 states only that compliance is verified and gives a return shape; it does not disclose side effects, whether tests or builds are run, permission requirements, or how the boolean flags constrain 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 compact and front-loads the purpose before the return shape; there is no filler. It could be considered slightly under-specified, but as a conciseness and structure measure it is appropriately brief.

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?

Despite having an output schema, the description is incomplete for a tool with 9 parameters and no annotations. It gives the return shape but leaves critical context unexplained: what compliance means, what 'options' should contain, and what the allow_* flags control.

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%, and the description adds no meaning to any of the 7 boolean parameters or the required 'options' object. It only mentions the 'path' placeholder, leaving the other parameters completely unexplained.

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 uses a specific verb ('Verify') and resource ('Test-Driven Development (TDD) compliance at <path>'), which clearly states what the tool checks and where. It does not explicitly distinguish itself from related sibling tools like rush_test or rush_coverage, so it stops short of a 5.

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 instead of alternatives, or what scenarios require TDD compliance verification. The description only implies that it operates on a path; it does not mention prerequisites, exclusions, or contrasts with sibling tools.

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