Delete Post-Install Script

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Delete', which implies destruction, but does not clarify if the action is irreversible, any side effects, or confirmation of success. For a delete operation, this is insufficient 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 a single sentence that is concise and front-loaded with the essential action. Every word earns its place, with no superfluous information.

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 low complexity (one parameter, no output schema, no annotations), the description is adequate but lacks explicit mention of return behavior or prerequisites. An agent might wonder if deletion succeeds or if the script must exist. It meets minimal 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 description coverage is 100% (parameter 'id' is described as 'Post-install script ID'). The description adds no additional meaning beyond the schema, meeting the baseline for high coverage. No extra details like format or source of the ID are provided.

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 'Delete' and the resource 'post-install script' with the specific identifier 'by its ID'. It is unambiguous and distinguishes from sibling tools like 'create_post_install_script' and 'list_post_install_scripts'.

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 does not provide explicit guidance on when to use this tool or mention alternatives. It implies the need for an ID, but no context on prerequisites (e.g., script must exist) or when to choose delete over update. However, the purpose is straightforward and sibling names are clear.

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