get_console_output

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is already conveyed. The description adds the diagnostic intent but does not disclose any additional behavioral traits such as potential rate limits, output size, or required permissions. Since annotations cover the read-only nature, the description is adequate but not rich.

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 extremely concise — two short sentences packed with purpose and use case. There is no fluff or redundancy. Every part adds value, and the key action is front-loaded.

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 (2 params, output schema present, read-only annotations), the description covers the core action and purpose. However, the lack of parameter documentation is a notable gap in an otherwise complete picture, and the description could benefit from noting that it requires an existing VM identifier.

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 description provides no explanation of the parameters 'name_or_id' or 'lines'. With schema description coverage at 0%, the description must compensate, and it fails to do so. It does not even hint that one must specify an instance identifier or that the number of lines is configurable.

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: 'Read the serial console log of an instance' and adds a specific use case ('fastest way to diagnose a VM that boots but is unreachable'). It uses a specific verb (Read) and resource (serial console log of an instance), and the differentiation from sibling tools (like get_server) is implicit but clear.

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 provides a clear when-to-use scenario: 'the fastest way to diagnose a VM that boots but is unreachable.' It does not explicitly mention alternatives or when not to use it, but the context is sufficient for an agent to infer appropriate use.

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