Create Post-Install Script

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

No annotations are provided, so the description carries full burden. It does not disclose side effects (e.g., behavior on duplicate names, whether content is validated), permission requirements, rate limits, or the return format. For a mutation tool, this is a significant transparency gap.

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 short sentence, front-loaded with the purpose, and contains no fluff. It is appropriately concise but so minimal that it borders on under-specification, though for a simple create tool it is acceptable.

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?

The tool is simple, but with no annotations and no output schema, the description should provide more context. It lacks information about the response/return value, error handling, uniqueness constraints, or any behavioral expectations. The description is under-specified for a complete tool definition.

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% coverage: 'name' is described as 'Script name' and 'content' as 'Script content (bash)'. The description adds no additional parameter semantics. With full schema coverage, the baseline is 3.

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 ('post-install script'), which distinguishes it from sibling tools like vps_scripts_list, vps_scripts_get, vps_scripts_update, and vps_scripts_delete. The verb and resource are specific and unambiguous.

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 implies usage (when you need to create a new script), but it does not explicitly state when to use this tool over alternatives or provide exclusions. There is no mention of prerequisites, uniqueness constraints, or scenarios where another tool would be more appropriate. This is implied usage rather than clear guidance.

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