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

Annotations already communicate read-only, idempotent, and non-destructive behavior. The description adds useful behavioral details: it reflects a running pod's recent output and has a 30-second heartbeat freshness, which helps set expectations about data recency.

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 two short sentences with the core purpose stated first and supplementary context second. There is no redundant or extraneous wording.

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 simple read-only log-tail tool, the description covers what is returned, how fresh it is, and where to find the full log. It does not specify output formatting, but the tool's simplicity and annotations make the description sufficient for correct use.

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 fully documents the single required id parameter with an example, so the baseline is met. The description does not add extra parameter-specific semantics, but none are needed given the simple and obvious id field.

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 identifies the tool as returning the last <=20 thermo/log lines from a running pod, which is a specific and recognizable retrieval action. It also distinguishes itself from the full log by noting that the full log.lammps is in the results tarball.

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?

It provides useful context by mentioning the 30-second heartbeat and that the full log is in the results tarball, but it does not explicitly name sibling tools like job_results or state when to prefer this tail view over the full log. The guidance is implicit rather than direct.

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