tail_log

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

No annotations are provided, so the description carries the full disclosure burden. It usefully names the concrete file path and implicitly signals a read-only operation, but says nothing about default line count, truncation behavior, or what happens if minecraft/logs/latest.log is absent.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the terseness leaves no room for the missing parameter and behavioral detail.

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 conceptually simple read tool with no output schema, naming the exact log file path goes a long way toward completeness. The gaps are the undocumented default/limit for 'lines' and the absence of any failure-mode or prerequisite information.

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 0% for both parameters, so the description must compensate and does not: 'id' is never mentioned at all, and 'lines' is only obliquely implied by 'last lines' with no default, maximum, or unit stated.

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 ('Return') plus the exact resource and path ('the last lines of the instance's minecraft/logs/latest.log'), which is far more precise than a generic 'get log'. It does not distinguish itself from a sibling like diagnose_instance, which an agent might reasonably consider for troubleshooting.

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?

There is no guidance on when to reach for this tool versus diagnose_instance, nor on prerequisites such as whether the instance must be running or whether the log file must already exist. Usage must be inferred entirely from the tool name.

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