Get post-install scripts

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 that results are account-scoped and represent available automation scripts, which is mildly useful but does not disclose pagination behavior, return shape, or any additional side effects.

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 two sentences and front-loads the primary action and resource. The second sentence is slightly redundant with the first but adds the 'VPS deployment' context, so it earns its place without excessive verbosity.

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 read-only list operation with one optional pagination parameter and annotations covering safety, the description is mostly sufficient. It mentions account scoping and the domain of the scripts, though it does not explain pagination behavior or return fields, which would be helpful if the response format is non-obvious.

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 description coverage is 100%, so the only parameter 'page' is already documented in the schema as 'Page number.' The description adds no extra meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 uses a specific verb ('Retrieve') and resource ('post-install scripts associated with your account'), making the basic purpose clear. It does not explicitly differentiate itself from the singular sibling VPS_getPostInstallScriptV1, relying on the plural 'scripts' to signal listing behavior.

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 says 'Use this endpoint to view available automation scripts for VPS deployment,' which gives some usage context. However, it does not state when to prefer this over the singular retrieval tool or mention any exclusions or alternative tools.

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