Delete a custom skill

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

Annotations already signal destructiveHint=true and idempotentHint=true. The description adds meaningful behavioral context: only custom skills are affected, built-in skills are protected, and the skill is minor and re-creatable, which is why no confirmation is needed. This goes beyond the structured hints without contradicting them.

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?

Three short sentences with no filler. The core action and scope come first, the exclusion rule follows, and the final sentence provides useful operational context. Every sentence earns its place.

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 single-parameter delete tool, the description covers what can be deleted, what cannot, where to get the id, and why no confirmation is needed. Annotations cover safety and idempotency, so nothing essential is missing.

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%, and the id property is already described as 'the custom skill id (from list_skills)'. The description repeats this same information rather than adding new parameter-level meaning, so the baseline of 3 is appropriate.

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 states a specific verb ('Delete') and a clear resource ('one of the workspace’s CUSTOM skills'), scoped by id and sourced from list_skills. It also distinguishes this tool from related skill tools like get_skill, save_skill, and list_skills by emphasizing custom-only 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 says when deletion is allowed (custom skills) and when it is not (built-in skills/recipes can’t be deleted). It also tells the agent where to obtain the id (from list_skills), which is practical routing guidance for use.

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