coolify_stop

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

The description adds the 'DEFAULT DISABLED — COOLIFY_ALLOW_STOP must be true' prerequisite, which is beyond annotations, and mentions 'destructive', aligning with the destructiveHint annotation. However, it does not disclose other behavioral aspects like reversibility or effects on running resources.

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 extremely concise: a single statement and an important configuration warning. It is front-loaded with the primary action and contains no 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?

For a simple stop operation, the description plus annotations provide sufficient context: the action, destructive nature, and a critical configuration requirement. The schema covers parameters. It lacks mention of reversibility, but the existence of coolify_start as a sibling implies resources can be restarted, so this gap is minor.

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 input schema already provides descriptions for all three parameters (resource_uuid, resource_type, environment_name), so the description adds no additional parameter meaning. Baseline of 3 is appropriate given 100% schema coverage.

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 'Stop a resource' clearly states the action (stop) and object (resource), and the schema enumerates valid resource types. It distinguishes from siblings like 'start' and 'restart' by the verb, but does not explicitly compare or contrast.

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 no guidance on when to use this tool versus alternatives such as coolify_start or coolify_restart. The only additional note is the environment variable requirement, which is a prerequisite rather than usage context.

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