get_service_status

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

No annotations are provided, so the description carries the full burden. It conveys that this is a read-only status query against systemd, which implies no mutation, but it does not disclose potential behaviors such as authentication needs or behavior when the service is not found. The read-only nature mitigates the concern, but the description is still thin.

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 sentence with no filler. It front-loads the action and the resource, and every word contributes to the meaning.

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 two-parameter tool with an output schema, the description is close to adequate, but it leaves usage differentiation and parameter semantics underspecified. An agent can probably invoke it correctly, but not with strong confidence about when it is the best choice over sibling tools.

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%, so the description must compensate. It clarifies that 'service' is a systemd service and 'device' is a Pi, but does not define service name format, device scope, or how the two parameters interact beyond that. This adds minimal value over the raw parameter names.

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 uses a specific verb ('Get'), a specific resource ('detailed systemd status'), and scopes it to 'one service on a Pi'. This clearly distinguishes it from device-level status retrieval (get_raspberry_pi_status) and from log or control operations (get_service_logs, control_service).

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 intended use is implied by 'status for one service' versus the sibling tools, but no explicit when-to-use or when-not-to-use guidance is provided. An agent can infer it is for service-level status rather than logs or actions, but the description does not name alternatives or exclusions.

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