delete_feature_flag

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

Without annotations, the description adds the crucial 'WRITE, destructive' nature and required scopes. It could further detail what cascade effects occur or idempotency, but it provides adequate transparency for safe use.

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 sentences, front-loads the purpose, and includes only essential information. No wasted words.

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 no output schema, the description covers the action, prerequisites, and destructive nature. It could mention what happens after deletion (e.g., no return value), but it is nearly 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?

Schema description coverage is 100%, so the schema already explains each parameter. The description does not add extra meaning beyond 'by key', remaining at baseline.

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' and the resource 'feature flag', and specifies it is destructive. This distinguishes it from sibling tools like create_feature_flag or list_feature_flags.

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 lists required permissions and environment variable, providing clear prerequisites. It does not explicitly mention when not to use it or alternatives, but the context is sufficient for a deletion tool.

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