Create custom Ploi server

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

The description adds value by stating the return value (SSH command/start URL), but beyond the annotations (non-readonly, non-destructive), it does not disclose additional behavioral traits such as prerequisites, side effects, or authentication requirements.

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?

Single sentence of 15 words, efficiently communicates the core purpose and return value with no unnecessary information.

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 creation tool with 3 parameters and no output schema, the description provides essential info (return value), though it could mention output structure or uniqueness constraints.

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 100%, so the description does not add new meaning to parameters. It does not explain parameter format or constraints beyond what the schema provides.

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 the action ('Create') and the resource ('custom server record'), and specifies the return value (SSH command/start URL). It effectively distinguishes from siblings like ploi_create_server and ploi_start_custom_server_installation.

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 vs alternatives. With siblings like ploi_create_server and ploi_start_custom_server_installation, the description should provide context on when to choose custom server creation over other options.

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