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: it explains this is a convenience tool configured for specific documents, mentions it generates PDF files, describes the optional save_path behavior (auto-generates if not provided), and specifies the return format. It doesn't mention authentication, rate limits, or error handling, but covers core behavior adequately.

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 usage guidance, example, and parameter details. The example query is detailed but necessary. Slightly long but every section earns its place. Could be slightly more concise in the example formatting.

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 4 parameters with 0% schema coverage and no annotations, the description provides complete context: clear purpose, detailed usage instructions with sibling tool integration, parameter explanations with examples, and mentions the return dictionary. The output schema exists, so return values don't need explanation. Excellent coverage for this complexity level.

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 explaining all 4 parameters: invoice_id is the debit/credit note ID with examples, legal_entity is the company code with examples, save_path is optional with auto-generation behavior, and profile has a 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 tool downloads a specific report type (debit/credit note) as PDF from D365FO, using the CustDebitCreditNoteController. It distinguishes from sibling tools like d365fo_download_customer_invoice by specifying it's for adjustment documents, not regular invoices.

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 (for debit/credit notes) and when to use an alternative (d365fo_query_entities to find available documents first). It includes a complete example query and specifies the entity and key fields needed for preparation.

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