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 crucial context beyond the basic 'delete' action by stating that deletion cascades to 'all features and environments in the project', which is valuable for understanding side effects. However, it doesn't cover other behavioral traits like permissions required, irreversibility, or error conditions, leaving gaps for a mutation tool.

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 two sentences that efficiently convey the core action and critical side effect. Every word earns its place, with no redundant or vague language, making it easy for an 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 mutation with no annotations and no output schema, the description is minimally adequate. It covers the cascading deletion effect, which is essential context, but lacks details on permissions, confirmation steps, or return values. For a high-stakes delete operation, more completeness would be beneficial, but it meets the basic threshold.

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 input schema has 100% description coverage, with the parameter 'idOrKey' well-documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or validation rules. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't detract either.

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 project'), making the purpose unambiguous. It distinguishes this tool from siblings like 'archive_feature' or 'delete_feature' by specifying it deletes projects, not features. However, it doesn't explicitly differentiate from 'update_project' or 'get_project' in the same sentence, which keeps it from a perfect score.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing project ID/key, or compare it to siblings like 'archive_feature' for non-destructive options. There's no explicit when/when-not usage context, leaving the agent to infer based on the name alone.

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