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 mentions the tool makes POST requests and returns a dictionary with response data and metadata, which is helpful. However, it doesn't cover important behavioral aspects like authentication requirements, error handling, rate limits, or whether the operation is read-only or destructive. The description adds some value but leaves significant gaps.

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 a clear purpose statement, parameter explanations, return value description, and practical examples. Every sentence earns its place, though it could be slightly more concise by integrating the example syntax more tightly with the parameter explanations. The front-loaded purpose statement is effective.

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 complexity of a generic service invocation tool with 5 parameters, 0% schema description coverage, no annotations, and no output schema, the description does a decent job but has gaps. It explains parameters well and provides examples, but lacks information about authentication, error responses, rate limits, and specific behavioral constraints. For a tool that could perform various operations (some potentially destructive), more context would be helpful.

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%, so the description must fully compensate. It provides excellent parameter semantics: it clearly explains all 5 parameters (service_group, service_name, operation_name, parameters, profile) with examples and clarifies that 'parameters' is optional. The examples show both with and without parameters, making the usage clear beyond what the bare schema provides.

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: 'Call a D365 F&O JSON service endpoint using the /api/services pattern' and 'provides a generic way to invoke any JSON service operation in D365 F&O.' It uses specific verbs ('call', 'invoke') and distinguishes itself from siblings by focusing on JSON service operations rather than entity operations, actions, or other specific tasks.

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: for invoking JSON service operations in D365 F&O via the /api/services pattern. It doesn't explicitly state when not to use it or name specific alternatives, but the generic nature of the tool and the sibling list (which includes more specific tools like d365fo_call_action) imply it's for JSON services specifically.

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