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 action (export to a file) but lacks details on permissions required, whether it overwrites existing files, file format (e.g., JSON, CSV), error handling, or rate limits. For a mutation tool (export implies writing a file) with zero annotation coverage, this is insufficient for safe and effective use.

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 concise, with a clear purpose statement followed by separate 'Args' and 'Returns' sections. Every sentence adds value without redundancy, making it easy to scan and understand quickly. No unnecessary information is included.

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 (export operation with file I/O), no annotations, and an output schema present (which handles return values), the description is moderately complete. It covers the basic action and parameter but lacks behavioral context like file handling or error scenarios. With output schema reducing the need to explain returns, it meets a minimum viable level but has clear gaps for safe operation.

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 description includes an 'Args' section that documents the single parameter 'filePath' with a brief explanation ('Path where to export the profiles'). However, schema description coverage is 0%, and the description doesn't add crucial details like path format (absolute/relative), file extensions supported, or validation rules. It compensates slightly but not fully for the schema gap, aligning with the baseline when schema coverage is low.

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: 'Export all D365FO environment profiles to a file.' It specifies the verb (export), resource (D365FO environment profiles), and destination (a file). However, it doesn't explicitly differentiate from sibling tools like 'd365fo_import_profiles' or 'd365fo_list_profiles' beyond the export action, which is why it doesn't reach 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 prerequisites, such as needing existing profiles to export, or compare it to siblings like 'd365fo_get_profile_names' or 'd365fo_list_profiles' for viewing profiles without exporting. This lack of context leaves the agent to infer usage scenarios.

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