ms-fabric-mcp-server

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

With no annotations provided, the description carries full burden. It explains the tool's behavior ('Retrieves an existing pipeline, adds a Notebook Activity to it, and updates the pipeline definition') and mentions default values for some parameters. However, it doesn't disclose important behavioral aspects like error handling, permission requirements, rate limits, or whether the operation is idempotent, which are significant 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 well-structured with clear sections: purpose statement, usage guidelines, parameter list, and return value. Every sentence adds value, with no redundancy. The parameter explanations are terse but informative, and the 'Use this tool when:' section is front-loaded for quick decision-making.

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 (11 parameters, mutation operation) and no annotations, the description does a good job explaining purpose, usage, parameters, and return values. The output schema exists, so the description doesn't need to detail return values. However, for a mutation tool with no annotations, it could better address behavioral aspects like error conditions or side effects.

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 provides substantial parameter information beyond the bare schema. It lists all 11 parameters with brief explanations of their purpose, including which are optional and default values for timeout, retry, and retry_interval_seconds. While it doesn't provide exhaustive details like format constraints, it compensates well for the schema's lack of descriptions.

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 ('Add a Notebook Activity'), target resource ('to an existing Fabric pipeline'), and mechanism ('appended to any existing activities'). It distinguishes from sibling tools like 'add_copy_activity_to_pipeline' by specifying the activity type (Notebook) rather than generic or other activity types.

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 includes an explicit 'Use this tool when:' section with three bullet points that clearly outline appropriate scenarios: when you have an existing pipeline, are building complex pipelines, or want incremental pipeline building. This provides clear guidance on when to select this tool over alternatives.

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