lua_execute

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

Describes that it runs arbitrary Lua code and captures output, but does not disclose potential risks, side effects, or permissions needed. With no annotations, more context on safety would be helpful.

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 that are front-loaded and to the point, with no wasted words.

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 tool with no output schema, it effectively covers what it does, its usage context, and what to expect in return. Minor lack of error handling details.

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?

Though schema coverage is 0%, the description adds meaning by specifying that the 'code' parameter is a Lua script and that it will capture print output and return value, which is beyond 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?

Clearly states it runs arbitrary Lua code in Cheat Engine and captures output. Distinguishes itself as an 'escape hatch' for when no dedicated tool covers the need.

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?

Explicitly says 'Use when no dedicated tool covers what you need,' providing clear guidance on when to use this tool instead of siblings.

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