Game Get Logs

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that it returns 'new print output' from the running game, implying it only fetches unread logs. However, it does not explain if logs are marked read after fetch, or behavior when no logs exist.

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 short but truncated ('runnin…'), which makes it incomplete. While concise, the truncation harms clarity and reduces its effectiveness.

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 the simplicity of the tool (1 optional param, no required params, output schema present), the description covers the basic behavior but fails to differentiate from similar tools or provide usage context. Annotations cover safety. Overall adequate but not complete.

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?

One parameter 'maxItems' with schema description 'Maximum unread log lines returned.' is clear. The tool description adds 'new print output' which aligns but does not provide additional meaning beyond the schema. With 100% schema coverage, baseline 3 is appropriate.

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 'Get new print output from the runnin…' combined with the tool name and parameter 'maxItems' (unread log lines) clearly indicates a read operation for new/unread logs from a running game. However, the truncation of 'runnin…' slightly reduces clarity and completeness.

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 like 'game_get_errors'. The description lacks context for selection among sibling tools, which is critical for an AI agent to choose correctly.

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