monitor_output

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

With no annotations, the description carries full responsibility for behavioral disclosure. It says 'Read' implying non-destructiveness, but does not explain that output is accumulated, that reading may or may not clear it (despite the 'clear' parameter), or whether the tool blocks or returns immediately. Missing important behavioral context.

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 a single terse sentence, which is highly concise and front-loaded. However, it is so brief that it borders on under-specification, overlooking additional context that could be added without sacrificing conciseness.

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 and no output schema, the description must compensate. It fails to explain what 'process output' entails, the return format, and the semantics of reading vs. clearing. The description is too minimal for the context.

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 schema covers the single 'clear' parameter with its own description and default value. The tool description adds no additional meaning about the parameter. Given 100% schema coverage, the baseline of 3 is appropriate.

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 'Read Godot process output' clearly identifies the action (read) and the resource (Godot process output), distinguishing it from other read tools in the sibling list. It is specific enough to convey what the tool does, though it could clarify what 'process output' refers to (e.g., stdout/stderr of a running project).

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 no guidance on when to use this tool versus alternatives like 'get_status' or runtime tools. It does not mention whether it is for running projects, what to do if no output exists, or any prerequisites.

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