Delete a custom skill

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

Annotations already indicate destructiveHint and idempotentHint, but the description adds useful context: it is 'Minor + re-creatable' and explicitly states no confirm is needed. It also discloses the constraint that built-in skills cannot be deleted, which is behavioral info beyond the annotations. There's no contradiction with the 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?

Two sentences with no fluff. The primary action and scope are front-loaded, followed by the exclusion and confirmation guidance. Every sentence adds value.

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 with no output schema and annotations covering safety, the description is sufficient. It covers what is deleted, how to identify it, what's excluded, and the confirmation behavior. 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%, with the id parameter already described as 'the custom skill id (from list_skills)'. The description essentially repeats this source reference, adding no new semantic detail beyond what the schema provides. Baseline 3 is appropriate given the high schema coverage.

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 verb ('Delete'), the resource ('workspace's CUSTOM skills'), and the scope ('by id (from list_skills)'). It also distinguishes custom skills from built-in skills/recipes, which are explicitly excluded. This differentiates it from any other delete operations in the sibling list.

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 provides explicit when-to-use context: delete custom skills, not built-in ones. It also gives the source of the id (list_skills) and explains that no confirmation is needed due to the minor, re-creatable nature, guiding the agent on when it's safe to proceed.

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