unity_console_log

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

No annotations provided, so description carries full burden. Only states the action without disclosing behaviors like whether it's non-destructive, number of messages returned, or output format. Minimal behavioral context beyond the action.

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 sentence is concise and front-loaded with purpose. However, could be more structured with explicit sections. Each word earns its place.

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?

With 3 parameters and no output schema, description lacks return format details. Does mention port for parallel-safe routing and refers to unity_select_instance, which is helpful. Adequate for a simple tool but incomplete for fully guiding an 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?

Input schema covers all 3 parameters with descriptions (count, type, port). Description adds no additional meaning beyond schema. Baseline of 3 since schema coverage is 100%.

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?

Description clearly states it gets recent Unity console log messages (errors, warnings, info) and that it's useful for debugging. Distinguishes from sibling tools like unity_console_clear (clears console) and unity_get_compilation_errors (gets compilation errors).

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?

Says 'Useful for debugging' but provides no explicit when-to-use vs alternatives (e.g., when to use this vs unity_console_clear or unity_get_compilation_errors). Usage is implied but not differentiated.

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