Dynamics 365 Finance & Operations MCP Server

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

No annotations are provided, so the description carries full burden. It states the tool clones with 'optional modifications' but doesn't explain what modifications are possible, whether cloning is destructive to the source, authentication requirements, rate limits, or error handling. For a mutation tool with zero annotation coverage, this lacks critical behavioral details.

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: the first sentence clearly states the purpose, followed by a concise 'Args' and 'Returns' section. Every sentence earns its place with no wasted words, making it easy 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 (cloning with modifications), lack of annotations, and 0% schema description coverage, the description is moderately complete. It covers parameters and mentions optional modifications, but an output schema exists (returns a 'Dictionary with cloning result'), so it doesn't need to detail return values. However, it misses behavioral aspects like side effects or error cases.

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%, but the description compensates by listing all three parameters with brief explanations: 'sourceProfileName: Name of the profile to clone', 'newProfileName: Name for the new profile', and 'description: Description for the new profile'. This adds meaningful context beyond the bare schema, though it doesn't detail constraints like character limits or uniqueness.

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 action ('Clone an existing D365FO environment profile') and resource ('profile'), which is specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'd365fo_create_profile' or 'd365fo_update_profile', missing an opportunity to clarify when cloning is preferred over creating from scratch or modifying existing profiles.

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 (e.g., needing an existing profile to clone), compare to 'd365fo_create_profile' for new profiles, or specify scenarios where cloning is beneficial (e.g., duplicating configurations). This leaves the agent without context for tool selection.

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