stack_services

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

Annotations already declare readOnlyHint and destructiveHint. The description adds value by detailing the parsing method (`--format '{{json .}}'`) and specifying the exact return format (list of dicts with keys id, name, mode, replicas, image, ports). This goes beyond the 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?

The description is concise: one main sentence plus a structured args/returns section. It is front-loaded with the core purpose. Minor inefficiency: the args documentation could be integrated into the description, but overall it's well-organized.

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?

Given no output schema, the description provides return format details. It explains filters with an example. However, it omits what happens if the stack does not exist or if no services match. For a simple list tool with good annotations, this is mostly complete.

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 both parameters: `name` is the stack to list services for, and `filters` is described with an example and behavior (list value repeats filter). This provides crucial context absent from the schema.

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 'List the services of a stack' with a specific verb and resource. It also mentions the format parsing. However, it does not explicitly distinguish from sibling tools like service_list or stack_ps, which could cause confusion.

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 usage when you need services for a specific stack, but provides no explicit guidance on when to prefer this over alternatives (e.g., service_list for all services, stack_ps for tasks). There are no exclusions or when-not scenarios.

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