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. While it mentions the creation action and returns a 'dictionary with creation result', it lacks critical details: whether this persists the profile permanently, what permissions are required, if there are rate limits, error conditions, or side effects. For a creation tool with zero annotation coverage, this is insufficient.

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 (Args, Returns) and efficiently documents many parameters. However, the opening sentence could be more front-loaded with key constraints, and some parameter explanations are verbose. Overall, it's appropriately sized for the complexity but not perfectly optimized.

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 creation tool with 13 parameters, 0% schema coverage, no annotations, but with an output schema, the description is partially complete. It excels at parameter documentation but lacks behavioral context, usage guidelines, and error handling. The output schema reduces the need to explain return values, but other gaps remain significant.

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?

Given 0% schema description coverage, the description fully compensates by providing detailed parameter documentation. It lists all 13 parameters with clear explanations, including defaults, optionality, and complex nested structures for credentialSource. This adds significant value beyond the bare schema, making parameter usage understandable.

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 ('Create a new D365FO environment profile') and distinguishes it from siblings like d365fo_clone_profile, d365fo_update_profile, and d365fo_list_profiles. It specifies the resource type ('environment profile') and scope ('with full configuration options'), 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 no guidance on when to use this tool versus alternatives like d365fo_clone_profile or d365fo_import_profiles. It mentions no prerequisites, dependencies, or typical use cases, leaving the agent without context for tool selection among the many profile-related siblings.

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