Featureflow MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by specifying permission requirements, which is crucial for a destructive operation. However, it lacks details on whether deletion is permanent, if there are confirmation prompts, rate limits, or what happens to associated data. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 extremely concise and front-loaded, consisting of just two sentences that efficiently convey the core action and a critical constraint. Every word earns its place, with no wasted text or redundancy, making it easy for an AI agent to parse quickly.

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?

Given the tool's complexity as a destructive operation with no annotations and no output schema, the description is somewhat incomplete. It covers the basic purpose and permissions but misses details on permanence, side effects, error handling, or return values. For a delete tool, this could lead to uncertainty about irreversible actions, though the permission hint adds some context.

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%, with the single parameter 'idOrUnifiedKey' well-documented in the schema. The description does not add any additional meaning or context about the parameter beyond what the schema provides. According to the rules, with high schema coverage (>80%), the baseline score is 3 even with no param info in the description, which applies here.

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 resource ('a feature flag'), making the purpose immediately understandable. It distinguishes from siblings like 'archive_feature' by specifying permanent deletion rather than archiving. However, it doesn't explicitly contrast with other destructive siblings like 'delete_environment' or 'delete_project'.

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 some guidance by mentioning permission requirements ('Requires production editor or admin permissions'), which helps determine when the tool can be used. However, it doesn't explicitly state when to use this versus alternatives like 'archive_feature' (for reversible removal) or clarify if deletion is permanent versus recoverable. No explicit exclusions or detailed context about alternatives is provided.

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