get_service_status

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

With no annotations, the description carries the full burden. It explicitly states 'Read-only -- never starts/stops the unit,' which is a key safety disclosure. It also details the execution context (WSL vs native systemctl) and lists the returned fields, adding transparency beyond the bare schema.

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 compact sentences that front-load the purpose, then add the command detail and safety note. Every phrase earns its place; the WSL/native distinction is relevant without being verbose.

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 zero-parameter tool with an output schema, the description is fully complete. It states what the tool does, the execution environment, the specific return data, and the critical read-only constraint. Nothing essential is missing for an agent to select and invoke it correctly.

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 tool has zero parameters, and the description adds no parameter-specific detail beyond mentioning the distro placeholder in the underlying command. Since the schema already fully covers parameters (none), the baseline of 4 applies.

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 states it reports the systemd unit status for the vLLM service, describing both the underlying command and the specific data returned. This distinguishes it from sibling tools like check_health (likely HTTP health) or get_gpu_status (hardware status).

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 implies use when systemd unit status is needed, but it does not explicitly contrast with alternatives or state when not to use it. No explicit when/when-not guidance is provided, though the read-only note hints at suitable contexts.

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