game_get_errors

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

The description reveals that the tool is stateful ('since last call'), which is important behavioral information beyond the schema. However, it does not disclose safety traits (e.g., whether it's read-only) or potential side effects, leaving gaps since annotations are absent.

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?

Single, front-loaded sentence with no redundancy. Every word is necessary 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?

Despite a single parameter and no output schema, the description omits return format details and how errors differ from logs (sibling tool). Given the sibling context and lack of annotations, the description is too sparse to fully inform the agent.

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 coverage is 100% (maxItems is described). The description adds no extra parameter-level detail; the schema already defines the parameter adequately. Baseline of 3 applies.

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 specifies the action ('get new') and resource ('push_error/push_warning messages since last call'), distinguishing it from siblings like game_get_logs. It identifies the tool's purpose succinctly.

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 provides no guidance on when to use this tool versus alternatives (e.g., game_get_logs) or when not to use it. It does not mention prerequisites or context.

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