coolify_start_database

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

No annotations are present, so the description must fully disclose behavioral traits. It does not mention what happens if the database is already running, whether the operation is idempotent, or any side effects. The description is too minimal to convey operational risks.

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?

At three words, the description is very concise but lacks any structural elements like paragraphs or bullet points. It earns its place by being to the point, but it may be too sparse for an agent to fully understand the tool's purpose without additional context.

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 tool with one parameter and no output schema, the description covers the basic operation. However, it does not explain what 'start' entails (e.g., does it succeed if already running?) or provide any confirmation of success. It is minimally adequate but leaves important questions unanswered.

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 100% description coverage for the 'uuid' parameter ('Database UUID'). The description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate since the schema already handles parameter semantics.

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 'Start a database' uses a clear verb+resource pattern. It unambiguously indicates the action (start) and resource (database), and it effectively distinguishes this tool from sibling tools like stop, restart, get, etc.

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. There is no mention of prerequisites (e.g., database must exist and be stopped), conditions, or exclusions. An agent has no context about appropriate scenarios for invocation.

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