rush_context_mistakes_check

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

No annotations are supplied, so the description carries the full burden. 'Check' suggests a read-only inspection, but the description never states that it does not modify the repository, what permissions are needed, or any other behavioral traits. It does not contradict anything, but it omits the safety profile entirely.

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?

A single front-loaded sentence with no filler. It conveys the action and target in ten words. It is short rather than over-specified, so appropriateness is high.

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 zero-parameter tool with an output schema, the description is mostly sufficient. Gaps remain: what counts as a 'mistake' or 'anti-pattern', which repository/history is checked, and when to invoke this tool relative to its siblings. This is adequate but not complete.

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?

The input schema has zero properties, so there is nothing to document; schema coverage is trivially 100%. No parameter explanation is needed, and the description adds no irrelevant parameter details.

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?

States a specific action ('Check') and resource ('git revert history'), and identifies the subject as 'past mistakes and anti-patterns.' It doesn't explicitly differentiate from siblings such as rush_context_retrieve or rush_review, but the domain is distinct enough. Vague terms like 'mistakes' and 'anti-patterns' reduce clarity slightly.

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 on when to choose this tool over siblings, when it is appropriate, or when not to use it. The description gives no context, exclusions, or alternatives, so an agent must infer usage from the name alone.

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