Delete Feature Flag

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

The description explicitly notes 'Permanently delete', adding the irreversible nature beyond the annotations' destructiveHint. Annotations already convey destructive and idempotent hints, so the description adds some value but doesn't cover consequences like impact on dependent features or if deletion fails. 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?

One simple sentence, completely front-loaded with the action and resource. No waste.

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 is simple with one parameter and no output schema, but as a destructive operation it could benefit from noting side effects (e.g., permanent loss, cascading effects on agents using the flag). The description is minimal and lacks context about safe usage, especially given the destructive nature.

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 description covers 100% of the parameter ('Feature flag key'), so the description doesn't need to add much. It adds the notion of 'by key' in the description, which aligns with the schema. Baseline 3 applies due to high schema coverage, and the description adds minimal extra meaning.

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 tool permanently deletes a feature flag by key, using the specific verb 'delete' and identifying the resource. It doesn't explicitly distinguish from sibling tools like lyzr_update_feature_flag or lyzr_delete_module, but the resource and action are 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?

No guidance on when to use this vs. other feature flag tools (e.g., lyzr_get_feature_flag_admin, lyzr_update_feature_flag). It does not mention prerequisites such as needing to verify the flag exists or that deletion is irreversible, which would be useful context for an agent deciding between tools.

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