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 executes an action but doesn't clarify if this is a read-only or mutating operation, what permissions are required, potential side effects, error handling, or rate limits. For a tool with complex parameters and no annotations, this is a significant gap in transparency.

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 followed by 'Args:' and 'Returns:' sections. It's appropriately sized for a 6-parameter tool, with no redundant sentences. Minor improvements could include bolding key terms, but it's efficiently organized.

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 (6 parameters, nested objects, no output schema, and no annotations), the description is incomplete. It lacks details on return values (only 'Dictionary with action result'), error cases, authentication needs, and how to handle entity-bound vs. unbound actions. For a tool in a rich sibling set, this leaves critical gaps for an agent.

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 compensate. It lists all 6 parameters with brief explanations (e.g., 'action_name: Full name of the OData action to invoke'), adding meaning beyond the bare schema. However, it doesn't provide examples, format details, or constraints (e.g., how key_fields and key_values align), leaving some ambiguity.

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: 'Execute an OData action method in D365 Finance & Operations.' It specifies the verb ('Execute') and resource ('OData action method'), and distinguishes it from siblings like d365fo_call_json_service or d365fo_search_actions. However, it doesn't explicitly differentiate from all siblings (e.g., d365fo_create_entity_record), which keeps it from a perfect score.

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 when to choose this over d365fo_call_json_service or other action-related tools, nor does it specify prerequisites or contexts for invoking OData actions. This leaves the agent without usage direction.

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