extension_remove_script

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

The description adds behavioral detail by stating 'Returns True if a file was removed', which is useful. However, it does not disclose potential irreversible effects, error behavior when the script doesn't exist, or required permissions. With no annotations, the description carries the burden but only partially addresses it.

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 extremely concise, with two short sentences. It front-loads the core action and adds a relevant return-value note. There is no fluff or redundancy.

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?

While the tool is simple, the description omits essential context about parameter semantics and usage. The return value is mentioned, and the output schema may cover returns, but the lack of parameter guidance and any mention of related tools (like extension_list_scripts) makes it incomplete in context.

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 0% and the description does not explain the 'name' or 'category' parameters. The agent is left to guess what values are valid or what 'category' means, despite it having a default of 'Utility'. This is a significant gap.

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 'Delete' and resource 'installed script', clearly distinguishing it from sibling tools like extension_remove_fuse and extension_remove_dctl. It unambiguously states what the tool does.

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?

No guidance is given on when to use this tool versus alternatives, nor are prerequisites or exclusions mentioned. The action is obvious from the name, but the description does not provide context such as 'use to uninstall a script previously written with extension_write_script'.

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