game_get_logs

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

With no annotations, the description carries the full disclosure burden. It reveals the stateful, incremental behavior ('since last call'), which is useful and non-obvious. But it does not describe the return format, whether the log buffer is consumed, or what happens when the game is not running.

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?

A single concise sentence with no filler. The essential behavioral qualifier 'since last call' is included, making the description both efficient and informative.

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 no-parameter tool, this is mostly sufficient to invoke, but since there is no output schema the description does not state the return shape or edge-case behavior (e.g., empty output, game not running). It covers the main purpose but leaves some practical ambiguity.

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 schema has zero parameters, so there is no parameter detail to document. The description appropriately identifies the target resource (print output from the running game), satisfying the baseline for tools with no parameters.

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 states a specific verb and resource: get print output from the running game. The qualifiers 'new' and 'since last call' clarify the incremental nature, distinguishing it from siblings like game_get_errors and get_debug_output.

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 phrase 'since last call' implies a polling pattern: call repeatedly to retrieve only fresh output. However, the description does not explicitly say when to prefer this over game_get_errors or get_debug_output, nor does it mention any exclusions.

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