view_log

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

With no annotations provided, the description carries the burden of disclosure. It does explain the main behavior — returning recent captured stdout/stderr lines — which is useful. However, it does not mention limitations, behavior when no editor/project has launched yet, whether the buffer is persistent, or any side effects.

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 two sentences with no filler. It front-loads the core purpose and then adds the specific return behavior. Every 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?

For a one-parameter tool with no output schema and no annotations, the description is reasonably complete: it identifies the source of logs, the content type, and the return shape. It could be stronger by noting what happens when no prior launch/run exists, but this is a minor gap given the tool's simplicity.

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 description coverage is 100%, so the schema fully documents lineCount, including its default and max. The description adds only the phrase 'last N lines,' which aligns with the parameter but does not add meaningful semantic value beyond the schema.

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 a specific verb ('View') and a specific resource ('recent console output from the last launched editor or running project'). It also clarifies the return value ('last N lines of captured stdout/stderr'). However, it does not explicitly distinguish this from the sibling tool get_debug_output, which could plausibly serve a similar purpose.

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 implies when the tool is relevant: after an editor has been launched or while a project is running. It gives no explicit guidance on when not to use it, nor does it mention an alternative such as get_debug_output, so an agent must infer the appropriate context.

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