service_ps

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

Discloses that tasks carry Status (State/Message/ContainerStatus), DesiredState, NodeID, and Slot; explains why failures matter. Add value beyond readOnlyHint and destructiveHint annotations.

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?

Every sentence adds value: purpose, analogy, what info each task has, when to use alternatives, prerequisite, and clear argument/return list. No redundant text.

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?

Covers all necessary aspects: purpose, usage context, alternative tools, parameter details, return format, and prerequisite. Despite no output schema, the return description suffices. Fully complete for a list service tasks 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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: id_or_name is a service id/name, and filters lists valid keys (id, name, node, label, desired-state) with enum values. Also describes return list structure.

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?

Clearly states verb ('List'), resource ('a swarm service's tasks'), and provides analogy to 'docker service ps'. Explicitly distinguishes from sibling tools like container_list, stack_ps, and service-tasks resource.

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?

Provides explicit guidance on when to use this tool vs alternatives (container_list, stack_ps, service-tasks resource) and states prerequisite (requires a swarm manager). No ambiguity.

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