dokploy_project

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

No annotations provided, so description carries full burden. It mentions that list returns nested details and get returns same, but omits side effects (e.g., cascade on removal), permissions, rate limits, or pagination. The behavioral info is minimal.

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 a single sentence with clear action enumeration using colon separators. It is efficient and front-loaded with the verb 'Manage projects', though the structure could be slightly improved for readability.

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?

Given 6 parameters, no output schema, and no annotations, the description is incomplete. It lacks explanation of return values, the 'duplicateInSameProject' parameter, and prerequisites. Basic but insufficient for full agent guidance.

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 coverage is 0%, so description must compensate. It hints at parameters for each action (e.g., 'name' for create, 'projectId+fields' for update) but does not describe 'description' or 'duplicateInSameProject'. Only partial mapping from actions to schema parameters.

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 clearly states it manages projects and lists specific actions (list, get, create, update, remove, duplicate) with brief parameter hints. It differentiates from sibling tools like dokploy_environment by focusing on the project resource, though it doesn't explicitly contrast them.

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 on when to use this tool versus alternatives (e.g., dokploy_environment for environments). The description only enumerates actions without context of when each is appropriate.

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