speedhack

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

No annotations are provided, so the description must cover behavioral traits. It states 'Affects the game's perception of time' but fails to disclose whether the change is destructive, persistent, or requires specific permissions. Minimal transparency for a mutation tool.

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 unnecessary wording. Front-loaded with the action and provides critical examples immediately. Every word earns its place.

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 simple one-parameter tool with no output schema, the description covers the essential aspects: what the parameter does and its effect. Minor gap: does not specify if the speed persists or if there are bounds, but overall sufficient.

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 single parameter 'speed' has no schema description (0% coverage). The tool description compensates by explaining the meaning of values (1.0 normal, 2.0 double, 0.5 half), providing essential context that the schema lacks.

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 'Set the speedhack multiplier' with specific verb and resource. Examples (1.0=normal, 2.0=double, 0.5=half) add precision. Distinguishes from siblings by focusing on time perception alteration, unique among listed tools.

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?

Provides context for three specific speed values, implying typical usage, but offers no guidance on when to use this tool versus alternatives (e.g., lua_execute) or when not to use it. No prerequisites or exclusions are mentioned.

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