Godot Runtime Logs

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

No annotations are provided, so the description carries full burden. It doesn't disclose whether reading logs is destructive, whether recent logs are retained upon restart, whether logs are ordered, or how far back they reach. The phrase 'from the managed process or bridge' hints at a dual source but offers no further behavioral detail.

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?

Extremely short at one sentence, which is efficient, but the brevity comes at the cost of substance. It's not well-stocked with the detail needed to justify its existence given the ambiguous 'managed process or bridge' phrasing.

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 tool with no annotations, no output schema, and 0% parameter schema coverage, the description is under-specified. It doesn't describe the return shape (array of strings? structured objects?), whether logs include timestamps/levels, or how limit affects output. Given constraints, this tool requires more descriptive support than it provides.

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 0%, so the description must compensate, but it doesn't explain the 'limit' parameter's meaning, units, range, or behavior (e.g., does limit truncate newest or oldest entries? what's the default?). The description provides zero parameter-specific information.

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 it returns runtime logs from 'the managed process or bridge' with a specific verb+resource. It distinguishes from runtime_status and runtime_perf but doesn't clarify what 'runtime logs' means in Godot context (GDScript print output? engine stderr? OS console?), and the reference to 'managed process or bridge' is ambiguous.

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 guidance on when to use this vs godot_runtime_status, godot_runtime_perf, or godot_editor_output. It doesn't clarify whether this captures script print/debug output, engine errors, or stdout/stderr, nor whether logs are polled, streamed, or pulled once. No exclusions or alternatives named.

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