VPS_getPostInstallScriptV1

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

No annotations exist, so the description carries full burden. It only states it retrieves details, but lacks disclosure on authentication, error behavior, or limitations. For a read operation, more context (e.g., 'returns script content and metadata') would improve 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?

Two clear sentences with no redundancy. The key information is front-loaded.

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?

Lacking an output schema, the description does not specify what 'details' are returned (e.g., script content, metadata). For a simple retrieval, it is minimally adequate but could benefit from mentioning response structure.

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% for the single parameter, and the description mirrors the schema ('by its ID'). It adds no extra semantics beyond what the schema already 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 ('Retrieve post-install script by its ID') and the resource ('post-install script', 'automation script details'). It distinguishes from sibling VPS_getPostInstallScriptsV1 by focusing on a single script via ID.

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 have a script ID and want details. It does not explicitly mention when not to use it (e.g., use VPS_getPostInstallScriptsV1 to list all) but the phrasing 'by its ID' provides adequate context.

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