Service Logs

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

No annotations are provided, so the description must carry the full behavioral disclosure. It only reveals the implementation command (journalctl -u) and does not explain access requirements, output volume, whether it blocks or follows, or side effects.

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 short phrase with no filler, and the identifying detail 'journalctl -u' is present. It is efficient, though slightly too terse to carry full context.

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?

Even though an output schema exists and the tool appears simple, the description omits parameter semantics and usage context needed to choose it reliably among many log-related siblings. It is not complete enough for confident invocation.

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 merely provides a generic optional 'params' object with additionalProperties true and 0% description coverage. The description hints at a unit filter via journalctl -u but does not explain how to specify the service name or which other journalctl options are accepted, leaving parameter construction ambiguous.

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 'Service logs via journalctl -u' identifies the resource (systemd service logs) and the mechanism used, which distinguishes it from sibling tools like docker_logs or k8s_logs. It lacks an explicit verb, but the intended action of retrieving logs is clear from the noun phrase.

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 when-to-use or when-not-to-use guidance and no alternative tools are mentioned. An agent must infer that this is for systemd services rather than for nginx, docker, kubernetes, or general linux logs.

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