Scale App

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

With no annotations provided, the description wisely discloses that the tool changes running process counts and requires a read-write mode plus confirmation. This meaningfully explains the side effects of calling the tool. It does not cover every possible nuance, but the key safety-relevant behavior is explicit.

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 two crisp sentences, front-loading the core operation and example, then adding side effects and prerequisites. No filler or repetition exists.

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 mutating tool with no annotations, the description covers the essential operational context: purpose, parameter format, side effects, and required mode/confirmation. An output schema exists, so return-value details are not necessary. It could be more explicit about what happens to omitted process types, but it is sufficient for correct 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?

Schema description coverage is 0%, so the description must add value. It clarifies the scale parameter with the concrete example 'web=2, worker=1' and states that confirm=True is required. The app parameter is minimally but sufficiently identified as the target Dokku app.

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 states a clear, specific operation: scaling process types for a Dokku app, with the format 'web=2, worker=1'. This is distinct from all sibling tools, none of which perform scaling. The example further clarifies the intended semantics.

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 gives useful preconditions: DOKKU_MCP_MODE=read-write and confirm=True. However, it does not provide explicit when-to-use or when-not-to-use guidance relative to alternatives like restart_app or set_config. Usage context is mostly implied by the tool's name and purpose.

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