fix_script_encoding

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

With no annotations, the description carries the full burden. It discloses the transformation (UTF-8 to Windows-874) and the triggering symptom, but does not state whether the file is modified in place, whether a backup is created, or how it behaves when the file is already correctly encoded.

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 sentences with no filler: the first states the action and resource, the second explains the exact failure scenario and target encoding. The key information is front-loaded and every clause contributes.

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 single-parameter utility with no output schema, the description adequately covers purpose, trigger condition, and conversion target. It omits only minor details like success/error response format and handling of files that are already valid.

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 only parameter, path, is already fully described in the schema as 'Path to the corrupted file'. The description adds useful context about file types and the corruption scenario but does not define path conventions such as absolute vs relative paths, so it adds limited value over the schema.

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 is verb-first ('Fix'), names a specific resource (.pwn/.inc file), and specifies the exact operation: converting mis-encoded UTF-8 Thai text back to Windows-874. It is clearly distinguishable from sibling file tools like read_pawn_script or compile_pawn.

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 gives an explicit trigger condition: use when another AI saved Thai text as UTF-8, causing garbled characters. It does not name alternative tools or state when not to use it, but the scenario is specific enough to guide selection among the file-related siblings.

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