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 and effectively discloses key behavioral traits: it's a destructive operation ('Removes'), has a failure condition ('fail if any other activity depends on it'), and specifies a prerequisite action. It doesn't cover aspects like authentication needs or rate limits, but provides sufficient context 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 front-loaded with the core purpose, followed by critical behavioral notes and parameter/return sections. Every sentence adds value—no redundancy or fluff—and it's structured for quick scanning with clear headings.

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 (destructive operation with dependencies), no annotations, and an output schema that covers return values, the description is complete enough. It explains the action, failure conditions, prerequisites, parameters, and return structure, leaving no critical gaps for an agent to invoke it correctly.

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 0%, so the description must compensate. It lists all three parameters with brief explanations (e.g., 'display name of the workspace', 'existing pipeline to update'), adding meaningful context beyond the bare schema. However, it doesn't detail format constraints or examples, leaving some ambiguity.

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 an activity from an existing Fabric pipeline') with the resource specified ('activity', 'pipeline'), and distinguishes it from siblings like 'remove_activity_dependency' by mentioning that tool as a prerequisite for handling dependencies.

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?

It explicitly states when to use this tool ('Delete an activity from an existing Fabric pipeline') and when not to use it ('This will fail if any other activity depends on it'), with a clear alternative named ('Use remove_activity_dependency to remove dependencies first'), providing comprehensive guidance.

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