test_fix_incremental_web

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

No annotations are provided, so the description carries the full burden. 'Fixing failures as they occur' implies the tool mutates code (potentially dangerous — modifies source files). It doesn't disclose what gets modified, whether changes are reversible, whether it commits, or whether it's a read-only test runner that suggests fixes vs actually applying fixes. The mutating behavior is under-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?

Single sentence, efficient, no wasted words. The sentence is compact and front-loaded with the core action. However it could benefit from being slightly longer to add usage guidance.

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 mutation-capable tool with no annotations and no output schema, the description is thin. It doesn't state what happens on failure (stops, continues, reports), how long it runs, what files it touches, or whether the spec param affects behavior. Given the complexity implied by 'fixing failures' and zero annotation coverage, more behavioral disclosure is needed.

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 100% — the single 'spec' parameter is fully documented in the schema with enum values (low/default/high) and a description. The tool description adds nothing about the param beyond what the schema states, which warrants the baseline 3. It doesn't clarify what each spec level means in terms of test coverage or resource usage.

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 states it runs tests incrementally for Next.js and fixes failures. It has a specific verb+resource+context (Next.js web app). However, it doesn't distinguish from siblings like test_fix, test_fix_incremental, or test_fix_web — 'incremental' and 'web' hints at the distinction but the description doesn't clarify what makes this tool unique vs test_fix_web or test_fix_incremental.

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 use this vs test_fix, test_fix_incremental, test_fix_web, or test_package. There are 23 sibling tools with overlapping concerns (implement_feature_web, test_fix_web, test_fix_incremental). The description gives no context about when this is appropriate — e.g., during development cycle, for CI, or for which repo/workspace context.

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