Deleting a custom script

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

Annotations already mark the tool as destructive (destructiveHint=true). The description adds the need for the 'confirm' parameter with 'YES' and the permission requirement, which is beyond what annotations provide. No contradiction with annotations.

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 very short (two sentences), but the first sentence repeats the title. Merging them would improve conciseness. Still, it is efficient and front-loaded with key info.

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?

The tool has low complexity, an output schema exists, and the description covers purpose and permission. However, it omits mention of the dry_run parameter's preview functionality, which is important for agent understanding. Lacks completeness for a delete tool with a preview option.

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 coverage is 100%, so baseline 3. The description adds no extra meaning beyond the schema for parameters like confirm, dry_run, and script_id. It only mentions the ID and permission, which are already covered.

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 explicitly states the verb 'Deleting' and the resource 'custom script', and distinguishes it from the many sibling tools like create_script, update_script, etc. It's specific and unambiguous.

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 mentions 'Perm: manage_scripts' which hints at a prerequisite, but does not explicitly state when to use this tool versus alternatives. Given the abundance of delete tools, some guidance on context would improve it.

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