transform_pawn_script

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

There are no annotations, so the description carries the burden of behavioral disclosure. It usefully reveals encoding preservation and the no-translation requirement, but it does not state whether the source file is modified, whether an existing target file is overwritten, or what happens on failure.

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 three short sentences, each earning its place: the core action with an example, the Thai-project usage requirement, and the no-translation constraint. There is no filler or redundancy.

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?

The core action, parameters, and Thai-specific constraints are present, which is enough for a straightforward invocation. However, with no output schema and no annotations, the description should say a bit more about target file creation/overwrite behavior and what the tool returns.

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%, so the baseline is 3. The Juice/Watermelon example reinforces the oldTheme/newTheme relationship, but the description does not add meaningful parameter semantics beyond what the schema already documents.

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 names a concrete action ('Clone and refactor a script') and clarifies the transformation with the example 'Juice -> Watermelon'. This is clearly distinct from sibling read/write/search/compile tools, so an agent can tell what this tool does without opening the schema.

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?

It explicitly states a mandatory usage context: 'MANDATORY for Thai projects to preserve encoding,' which tells the agent when to use this tool. It also adds a critical constraint ('DO NOT TRANSLATE Thai strings'), but it does not name alternatives or explicitly state when not to use it.

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