fix_encoding

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

With no annotations, the description must reveal behavioral traits. It mentions 'detect and repair' but does not clarify default behavior (dry_run=true means analysis-only) or potential side effects like file modification. The schema supplies dry-run semantics, but the description adds no behavioral context.

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 extremely concise at two sentences, delivering the core purpose and common context without wasted words. It is front-loaded with the main action.

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?

While the description explains what encoding issues it fixes and mentions Windows, it lacks information about return values, the analysis/repair process, and default behavior (dry_run). For a tool with no output schema, more detail on output or success indicators would improve completeness.

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 coverage is 100% with clear descriptions for both parameters (path and dry_run). The tool description does not add extra meaning beyond what the schema already provides, so a baseline score of 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?

The description clearly states the tool's purpose: fixing encoding issues, specifically BOM, broken UTF-8, and cp1252 artifacts. It uses a specific verb ('fix') and resource ('encoding issues'), and distinguishes itself from siblings like 'fix_umlauts' by listing concrete problems.

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 description implies usage when encoding problems are present, especially on Windows, but does not explicitly state when to use this tool over alternatives like 'fix_umlauts' or 'convert_format'. No exclusions or prerequisites are provided.

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