VPS_createPostInstallScriptV1

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

With no annotations, the description fully discloses key behaviors: script saved to /post_install, executable attribute set, execution after VM install, output to /post_install.log, and maximum size of 48KB. This provides comprehensive transparency.

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 concise with three clear sentences: purpose, behavior details, and usage. No unnecessary words, well-structured, and front-loaded with the main action.

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 the tool's simplicity (2 params, no nested objects, no output schema), the description covers core functionality, constraints, and use case. Minor gaps (e.g., error handling, execution user) are not critical for basic completeness.

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 schema already defines parameters. The description does not add significant new meaning beyond what the schema provides, offering only general context about content. Score is baseline 3 as per guidelines.

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 verb "Add" and the resource "post-install script", explaining its purpose for automation after VM installation. It distinguishes from sibling tools like VPS_deletePostInstallScriptV1 and VPS_updatePostInstallScriptV1 by focusing on creation.

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 explicitly says "Use this endpoint to create automation scripts for VPS setup tasks", indicating when to use. It lacks explicit when-not-to-use or comparison with alternatives, but the context implies creation vs. update or deletion.

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