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 convenience tool specifically configured for purchase orders, explains what purchase orders are, describes the return format (dictionary with download result), and mentions auto-generation of save paths. It doesn't cover potential errors, rate limits, or authentication requirements, but provides substantial operational 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, args, returns) and every sentence adds value. It's slightly longer than minimal but appropriately so given the complexity. The front-loaded purpose statement is excellent.

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 (4 parameters, 0% schema coverage, no annotations) and the presence of an output schema, the description is remarkably complete. It covers purpose, prerequisites, workflow integration, parameter semantics, and return format - providing everything needed for effective use despite the lack of structured documentation.

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?

With 0% schema description coverage, the description fully compensates by providing detailed parameter semantics: purchase_order_id format examples ('PO-000123'), legal_entity examples ('USMF'), save_path behavior (optional, auto-generates), and profile default value. This adds crucial 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 ('Download a purchase order report as PDF') and resource ('from D365 Finance & Operations'), with additional context about it being configured for purchase orders using PurchPurchaseOrderController. It distinguishes itself from sibling tools like d365fo_download_customer_invoice by specifying the document type.

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 vs alternatives: it instructs users to first query purchase orders using d365fo_query_entities with specific entity details (entity name, collection, key fields) and provides a concrete example query. This clearly establishes prerequisites and workflow integration.

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