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 the full burden of behavioral disclosure. It states the tool tests a connection and returns JSON results, but lacks details on what the test entails (e.g., network checks, authentication), potential side effects, error handling, or rate limits. This is insufficient for a tool that likely involves network operations.

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 concise and well-structured with a clear purpose statement followed by Args and Returns sections. However, the Args section could be more integrated into the main text, and some sentences (like the Returns line) are very brief but still informative, making it efficient overall.

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 lack of annotations and output schema, the description is incomplete. It does not explain what the JSON results contain, potential error scenarios, or how this tool differs from similar siblings like 'd365fo_test_profile_connection.' For a connection-testing tool in a complex environment, more context is needed for effective use.

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%, but the description adds some value by explaining the 'profile' parameter as optional and specifying it uses a default if not provided. However, it does not clarify what a 'profile' represents or how it affects the connection test, leaving gaps in understanding beyond the schema's basic type information.

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 tool's purpose as 'Test connection to D365FO environment,' which is a specific verb+resource combination. However, it does not explicitly differentiate itself from the sibling tool 'd365fo_test_profile_connection,' which appears to serve a similar function, leaving some ambiguity about when to use one over the other.

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, such as the sibling 'd365fo_test_profile_connection.' It mentions an optional profile parameter but does not explain the context for using it or any prerequisites, leaving the agent without clear usage instructions.

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