Dynamics 365 Finance & Operations 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 effectively describes key behavioral traits: it performs a mutation (setting a default), has side effects ('Automatically refreshes all cached client connections'), and explains the impact ('may affect client resolution for operations that use the default profile'). It also hints at the return format ('Dictionary with result including client refresh status'). However, it lacks details on permissions, error conditions, or rate limits.

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 and front-loaded with the core purpose, followed by behavioral context and clear sections for Args and Returns. Every sentence adds value: the first states the action, the second explains side effects, and the structured sections provide parameter and return details without redundancy. It is appropriately sized for the tool's complexity.

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 moderate complexity (a mutation with side effects), no annotations, 0% schema coverage, but an output schema present, the description is largely complete. It covers purpose, usage context, parameter semantics, and behavioral traits. The output schema handles return values, so the description need not detail them further. However, it could improve by mentioning prerequisites (e.g., profile existence) or error scenarios.

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 schema description coverage is 0%, so the description must fully compensate. It explicitly documents the single parameter 'profileName' with its purpose ('Name of the profile to set as default'), adding essential meaning beyond the schema's basic type information. This completely addresses the parameter semantics gap.

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 ('Set the default D365FO environment profile') and distinguishes it from sibling tools like 'd365fo_get_default_profile' (which retrieves) and 'd365fo_update_profile' (which modifies profile details). It uses a precise verb ('Set') with the target resource ('default D365FO environment profile'), making the purpose unambiguous.

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 clear context for when to use this tool by explaining that it 'Automatically refreshes all cached client connections since changing the default profile may affect client resolution for operations that use the default profile.' This implies it should be used when switching default profiles, especially if subsequent operations depend on the default. However, it does not explicitly state when NOT to use it or name alternatives (e.g., vs. 'd365fo_update_profile' for non-default changes).

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