unity_agent_log

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

No annotations are provided, so the description carries full burden. It discloses that only the last 100 actions are returned, which is a behavioral constraint. The description also implies read-only behavior (getting logs), which is appropriate. It does not contradict any annotations since none 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 a single, concise sentence that conveys all necessary information without extraneous details. It is well front-loaded with the tool's primary action and resource.

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 tool's simplicity (2 parameters, no output schema), the description adequately covers its purpose and key behavior (last 100 actions). It does not describe the return format, but without an output schema, that may be acceptable. The port parameter guidance is present in the schema.

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 input schema covers 100% of parameters with descriptions. The description adds no additional parameter details beyond the schema, but since schema coverage is high, the baseline is 3. The description's mention of 'last 100 actions' provides context not in schema, slightly elevating the score.

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 the tool's purpose: retrieving an action log for a specific agent, with the last 100 actions and timestamps. It uses a specific verb ('Get') and resource ('action log'), and distinguishes itself from siblings by being focused on agent logs, not other Unity operations.

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 does not explicitly state when to use this tool versus alternatives, but the context signals show many sibling tools with different purposes. The input schema provides guidance for the 'port' parameter, indicating its use for parallel-safe routing, which implies usage scenarios. However, no direct comparison to other logging or agent tools is provided.

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