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 explaining the tool generates reports via the D365FO SRS reporting engine, saves PDFs to specified locations, and returns a dictionary with download results. It could improve by mentioning authentication requirements, error conditions, or performance characteristics, but provides solid 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 (overview, args, common combinations, returns) but could be more front-loaded. The initial paragraph effectively communicates the core purpose, though the detailed parameter explanations are necessary given the complexity. Every sentence earns its place in explaining this multi-parameter tool.

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 (8 parameters, 0% schema coverage, no annotations), the description provides complete context including parameter semantics, usage examples, controller mappings, and output format. The presence of an output schema means the description doesn't need to detail return values, and it adequately covers all other aspects needed for effective tool invocation.

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 and 8 parameters, the description provides exceptional value by explaining each parameter's purpose, providing examples, defaults, and a comprehensive table mapping controllers to tables/fields. This fully compensates for the schema's lack of descriptions and gives the agent clear guidance on parameter usage.

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 SQL Server Reporting Services reports'), resource ('from D365 Finance & Operations'), and output format ('as PDF files'). It distinguishes from siblings by focusing on SRS report generation rather than direct document downloads like the specific invoice/purchase order tools, providing a more flexible alternative.

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 explicitly provides when to use this tool vs alternatives by listing common controller/table/field combinations and showing how it can generate various document types. It contrasts with sibling tools like 'd365fo_download_customer_invoice' by explaining this is a general SRS reporting engine approach rather than specialized document-specific downloads.

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