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. It explains what the tool does (downloads PDF reports) and mentions it's a 'convenience tool', but doesn't disclose important behavioral traits like authentication requirements, rate limits, error handling, or whether the operation is idempotent. It does mention the save_path behavior (auto-generates if not provided), which adds some context.

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 clear sections (purpose, usage guidance, example, parameters, returns). It's appropriately sized for the tool's complexity, though the example query section is quite detailed. Every sentence adds value, but some information could be more condensed.

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 has 4 parameters with 0% schema coverage and no annotations, the description does a good job explaining usage context, parameters, and provides an output schema (returns dictionary with download result). However, it lacks information about authentication, error cases, and system constraints that would be important for a download 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?

Schema description coverage is 0%, so the description must compensate. It provides meaningful context for all 4 parameters: explains what confirmation_id represents (with examples), what legal_entity is (with examples), the optional save_path behavior, and the default profile. However, it doesn't explain validation rules or constraints beyond examples.

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 ('Download a sales confirmation report as PDF'), the resource ('from D365 Finance & Operations'), and distinguishes it from sibling tools by specifying it's for 'sales order confirmations using the SalesConfirmController'. It differentiates from other download tools like d365fo_download_customer_invoice by focusing on sales confirmations.

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 explicit guidance on when to use this tool ('specifically configured for sales order confirmations') and how to find available confirmations using the d365fo_query_entities tool. It includes a detailed example query and references the specific entity and key fields needed, giving clear prerequisites and alternatives.

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