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 full burden and does well by disclosing key behaviors: it's a write operation (starts a session), downloads and caches metadata, and returns a session ID. It mentions fallback behavior for 'incremental' strategy but lacks details on rate limits, permissions, or error handling.

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?

Well-structured with purpose first, then parameters in a clear Args section, and return info. Slightly verbose in strategy explanations, but each sentence adds value. Could be more front-loaded by moving return details earlier.

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 3-parameter tool with no annotations and no output schema, the description is quite complete: covers purpose, parameters, and return type. Missing are details on output format (beyond 'dictionary'), error cases, and integration with sibling tools like d365fo_get_sync_progress.

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 fully explains all 3 parameters: 'strategy' with detailed enum-like options, 'global_version_id' with auto-detection behavior, and 'profile' with default usage. This adds significant meaning beyond the bare schema.

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 ('Start a metadata synchronization session') and the resource ('metadata from D365 F&O'), distinguishing it from siblings like d365fo_cancel_sync or d365fo_get_sync_progress. It explicitly mentions what gets downloaded (entities, schemas, enumerations, labels) and the return value (session ID for tracking).

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 implies usage by stating it 'returns a session ID for tracking progress,' suggesting it's for initiating syncs, but doesn't explicitly say when to use it versus alternatives like d365fo_get_sync_history or d365fo_cancel_sync. No guidance on prerequisites or exclusions is provided.

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