Remove Script

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the operation is non-destructive to the rest of the request, explains alias handling, and discloses the side effect of dropping the now-empty script container when all scripts are removed.

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 three sentences with purpose front-loaded, followed by usage guidance and a side-effect note. It is efficient but slightly dense, combining parameter semantics with behavior in one sentence.

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 delete tool with no annotations and no output schema, the description covers the core behavior, use cases, side effects, and parameter values adequately. Minor gaps exist around error conditions or return values, but these are not critical for a removal operation.

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%, with both parameters already having detailed descriptions. The description adds some context about canonical vs. alias scriptType values, but this is largely redundant with the schema's enum and field descriptions, so little new meaning is added.

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 (Delete) and the object (a script from a Bruno request), with specific script types listed. It also distinguishes itself from sibling tools by noting it leaves the rest of the request intact and referencing the tools that create 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 explicitly says 'Use this to undo or clean up a script written by create_request/modify_request/add_test_script', giving a clear when-to-use directive. It also clarifies that it removes scripts rather than the whole request, implicitly excluding delete_request.

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