delete_feature_set

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

The annotations already declare destructiveHint=true, and the description adds that deletion is 'Permanent, cannot be undone' and further restricts to non-shared templates. This provides meaningful behavioral context beyond the annotation without contradicting it.

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 two short sentences, front-loaded with the primary action 'Delete a custom feature set' and followed by essential warnings. Every word serves a purpose, making it very concise and well-structured.

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 tool with one documented parameter and a destructive annotation, the description provides necessary caveats (permanence and shared template restriction). The presence of an output schema means return value details are not required, so the description is sufficiently complete.

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 schema fully describes the sole parameter with 'UUID of the feature set to delete' (100% coverage). The description adds the context of custom feature sets but does not enhance the parameter's semantics beyond what the schema already provides.

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 'Delete a custom feature set,' using a specific verb and resource. It distinguishes from sibling tools by specifying 'custom' and explicitly excluding shared templates, which sets it apart from template-related operations.

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 implies usage for custom feature sets and notes the restriction 'Cannot delete shared templates,' but does not explicitly mention alternatives or provide when-to-use versus when-not-to-use guidance beyond this exclusion. This gives partial contextual guidance.

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