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

The description reinforces the destructive nature of the operation beyond the destructiveHint annotation by mentioning 'tier-locked' and 'Always allowed.' It does not mention irreversibility or side effects, but the word 'delete' and the annotation provide adequate 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, focused sentence with no redundant wording. It front-loads the action and target, and the additional permission context is compact and relevant.

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 delete operation with no output schema, the description provides necessary context about ownership and tier-locked restrictions. It does not specify return behavior or error cases, but those are commonly implicit for deletion tools.

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?

The only parameter, tool_name, is described as 'The script to delete,' which is accurate but minimal. Since the schema already fully covers this single parameter, the description adds limited extra semantic value.

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'), the target ('stored scripts'), and the selection mechanism ('by tool_name'). It also distinguishes this from sibling tools like script_get and script_save by focusing on deletion.

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?

It explicitly states when deletion is allowed ('Always allowed for your own company's rows') and includes a practical example ('deleting is how a downgraded account trims its vault'). It does not explicitly describe when to avoid using it, but the scope limitation is clear.

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