Get post-install script

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only a vague indication that the endpoint returns 'specific automation script details,' with no deeper context such as response format, permissions, or pagination. It is adequate but not enriching.

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 short and front-loaded with the core action. The second sentence is somewhat redundant with the first but still reinforces the specific-details use case without bloating the description.

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 single-ID read operation with one fully documented parameter and read-only annotations, the description is complete enough for an agent to select and invoke the tool correctly. No critical context is missing.

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%, and the single parameter is already described as 'Post-install script ID.' The description's 'by its ID' adds no meaningful semantic information beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: 'Retrieve post-install script by its ID.' It clearly distinguishes this singular get tool from its siblings such as VPS_getPostInstallScriptsV1 (list), VPS_createPostInstallScriptV1, and VPS_deletePostInstallScriptV1.

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?

'Use this endpoint to view specific automation script details' gives a clear context for when to call it: when the agent needs details for a known script ID. It does not explicitly name alternatives or state exclusions, but the usage intent is clear.

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