service_list_tool

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

With no annotations provided, the description fully discloses the filtering behavior (ExecStart contains /usr/bin/podman, non-container services excluded) and the return type (list with status). This is transparent and adds value beyond simple 'list' semantics.

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 compact and well-structured: a one-line summary, a two-bullet filter criterion, and a returns line. Every sentence earns its place with no redundancy or filler.

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?

The tool has no parameters and the output schema exists, so the description doesn't need to detail return fields. It fully specifies the filtering logic and the nature of the returned list, making it complete for this simple list tool.

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, so the schema is empty and there are no parameter semantics to explain. The description appropriately doesn't add parameter guidance, and a baseline of 4 is justified for no-parameter tools.

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 the tool lists systemd units that manage Podman containers, using a specific verb and resource. It distinguishes itself from siblings by specifying the ExecStart containing /usr/bin/podman filter and excluding non-container services.

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 provides clear context for when to use this tool: when you need only Podman-related systemd units. It implies exclusions (non-container services are not shown) but does not explicitly name alternative tools like service_list_tool, so it stops short of full 5.

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