App Domains

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

With no annotations present, the description explicitly covers the side-effect profile: 'Side effects: none (read-only).' It also names the exact Dokku command executed, adding transparency about how the result is produced. No annotation contradiction exists because no annotations were provided.

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?

Three short sentences; purpose is front-loaded, then side effects and implementation. No filler or redundancy.

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 one-parameter, no-nested-output tool, the description covers the core invocation requirements: what it does, that it is safe, and which command it wraps. The output schema covers return structure, so that is not a gap. It could be more complete by routing to siblings, but the core context is sufficient.

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 schema has 0% property descriptions, so the description must compensate. It adds limited meaning by situating the argument as the target Dokku app and showing it as <app> in the command template. It does not explain valid values, formats, or defaults, so the compensation is partial.

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?

Opens with 'Get domain / VHOST report for a Dokku app,' naming a specific action and resource. This cleanly separates it from siblings like app_report, app_config, or app_url, which target other aspects of an app.

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?

No guidance is given about when to prefer this tool over siblings such as app_report or app_url. The use case is implied by the domain/VHOST focus, but there are no exclusions, conditions, or alternative tool pointers.

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