Create App

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 explicitly discloses the side effect (creates an application on the Dokku host) and the mode requirement, which is essential for a mutating tool. It doesn't discuss duplicate-name behavior or reversibility, but the key mutation and prerequisite are stated.

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 three short sentences with the core action first, followed by side effects, a requirement, and a naming constraint. No filler or redundant restatement of the tool name.

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 single-parameter creation tool, the description provides the essential behavioral context: what it does, what it requires, and the accepted name format. It doesn't cover failure modes or uniqueness rules, but those are not necessary for basic selection and invocation.

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 has no description coverage for the `name` parameter, and the tool description compensates by specifying that app names must be lowercase alphanumeric with optional hyphens. It doesn't explicitly restate that the parameter is the app name, but that mapping is obvious from context.

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 (create) with a specific resource (a new Dokku app), making the tool's purpose immediately clear. It is distinct from sibling tools like list, logs, and restart, which handle different operations.

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 clearly states the prerequisite (DOKKU_MCP_MODE=read-write) and makes the intended operation obvious. It doesn't explicitly enumerate when not to use it or compare to alternatives, but among the given siblings, none are alternatives for creating an app.

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