gather

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

No annotations are provided, so the description carries the full burden. It states the intended action but does not disclose behavior around invalid targets, busy workers, ownership, cancellation of previous orders, or failure modes. This is minimal for a command that mutates game state.

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 one short sentence that immediately conveys the tool's purpose. There is no wasted text or unnecessary elaboration.

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 two-parameter command, the description is minimally viable: it names the actor and target. However, with no annotations, no output schema, and no usage guidance, the agent still lacks information about valid conditions, side effects, and error behavior.

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 0%, but the description helps by identifying worker_id as the worker and resource_id as a mineral/gas resource point. It does not explain where these IDs come from or how they are structured, so it only partially compensates for the lack of parameter descriptions.

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 clearly states that the tool commands a worker to gather a specified resource point (mineral/gas). It is specific enough to distinguish 'gather' from siblings like 'attack' or 'move', though it does not explicitly name an alternative.

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 no guidance on when to use this tool versus alternatives like move/attack, nor does it mention prerequisites such as worker readiness or proximity to the resource. Usage context is only implied by the word 'gather'.

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