fixAllLintErrors

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

Discloses behavior: uses VS Code source.fixAll when connected, falls back to linters. Annotations confirm destructive and idempotent. Description adds value beyond annotations.

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?

Two short sentences, front-loaded with purpose. No unnecessary words. Efficient.

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?

Given simple tool with one param, thorough schema coverage, clear annotations, and no output schema, description provides sufficient context including fallback behavior.

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?

Single parameter filePath is fully described in schema (100% coverage). Description does not add extra meaning, but baseline 3 is appropriate.

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?

Description clearly states it auto-fixes lint errors, names specific VS Code command (source.fixAll) and fallback linters (eslint/biome/ruff), distinguishing from sibling tools like applyCodeAction or formatDocument.

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?

Implied usage context: connected to VS Code uses source.fixAll, otherwise falls back to linters. No explicit when-not or alternatives, but clear enough for typical use.

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