shootFire in the direction you last moved. Hold the trigger longer to release multiple shots during gameplay.
Fire in whichever direction you last moved (there is no separate aim — facing is set by your last move). Holding longer fires multiple shots.
| Name | Required | Description | Default |
|---|---|---|---|
| holdMs | No | How long to hold the trigger, in milliseconds. Default 200. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description explains key behavior: direction from last move, no separate aim, holding longer fires multiple shots. Could mention ammo/cooldown but not critical.
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, direct, no 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?
Given simple tool, description covers action and parameter. Missing details like ammo but not necessary for basic use. No output schema so no return description needed.
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 describes holdMs fully; description adds effect of holding longer (multiple shots), adding meaning beyond 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 the action ('Fire') and specific behavior (direction based on last move). Distinguishes from siblings by describing its unique mechanic.
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?
No explicit guidance on when to use this tool versus alternatives. Gives mechanics but not selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.