Логи и ошибки

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

Annotations declare readOnlyHint=true and destructiveHint=false, yet mode=clear explicitly resets (destroys) the log buffer — a state mutation. The description therefore contradicts the declared read-only/non-destructive profile. This is an Annotation Contradiction.

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?

Three tightly packed sentences, front-loaded with the resource and then the mode semantics. No filler; each clause carries information, though the cursor/since sentence is slightly redundant with the schema's own since description.

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?

With no output schema, the description does hint at a response cursor, which is useful. However, for a 5-parameter, 0-required tool it leaves grep/level/limit unexplained and creates the readOnly-vs-clear inconsistency the agent must resolve.

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 only 40% (5 params). The description adds real meaning for mode (three value semantics) and for since (incremental reads via the response cursor), but grep, level, and limit remain undocumented anywhere. It also refers to a 'cursor' that does not appear as a distinct parameter, slightly muddling since.

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?

States a specific verb+resource: reading output (prints, errors, traces) from a running Godot instance, and enumerates the three modes. No sibling does log retrieval, so differentiation is implicit rather than stated, but the purpose is unmistakable.

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?

Explains what each mode does (tail = last lines, errors = errors/warnings with parsed stack traces, clear = reset buffer) and tells the agent to use the response cursor with since for incremental reads. Covers when to pick each mode, though it offers no explicit when-not guidance.

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