get_output

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

Annotations are minimal (destructiveHint=false), description adds behavioral context: output retrieval, no user visibility, and filter options. Does not mention side effects of clearing buffer, but overall transparent.

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?

Description is concise with clear sections: purpose, important note, usage advice, and parameter docs. Could be slightly trimmed, but well-structured and 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?

Covers usage, parameters, and important behavioral notes. No output schema, but hints at summarizing output. Sibling list shows many debug tools, but this one is unique. Adequate for its role.

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%, description fully documents both parameters: 'clear' (boolean, default false) and 'category' (stdout, stderr, console, default all). Adds meaning beyond 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 clearly states the tool retrieves stdout/stderr output from the debugged program, distinguishing it from siblings like get_output_tail and search_output. It also emphasizes that the user cannot see the output directly.

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?

Explicitly advises when to use (periodically during debugging) and how (read and summarize for user). Provides important instruction not to tell user to check console. Lacks explicit alternatives, but implied by siblings.

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