ms-fabric-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 states the tool deletes items but doesn't mention critical behavioral aspects like whether deletion is permanent, requires specific permissions, has confirmation prompts, or affects dependencies. The example shows a basic call but lacks context about consequences or error handling.

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 well-structured with clear sections (purpose, parameters, returns, example) and uses bullet points for readability. While somewhat verbose, each sentence adds value. The example is helpful but could be more concise.

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 destructive mutation tool with no annotations, the description is moderately complete. It explains parameters and return format, and an output schema exists. However, it lacks crucial behavioral context about deletion consequences, permissions, and error conditions that would be essential for safe usage.

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?

With 0% schema description coverage, the description compensates well by explaining all three parameters: workspace_name, item_display_name, and item_type. It provides examples of item types and lists supported values, adding meaningful context beyond the bare schema. However, it doesn't specify format constraints or validation rules.

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 specific action ('Delete') and resource ('item from a Fabric workspace'), distinguishing it from sibling tools like 'list_items' or 'create_semantic_model'. It explicitly mentions the item is identified by display name and type, providing clear differentiation.

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 is provided on when to use this tool versus alternatives. While sibling tools like 'delete_activity_from_pipeline' or 'delete_measures_from_semantic_model' exist for specific item types, the description doesn't mention these alternatives or provide context for choosing between them.

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