d365fo_download_sales_confirmation

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full burden. It mentions the return format (dictionary with download result) and that it uses SalesConfirmController. However, it does not disclose whether the operation is read-only or destructive, or if specific permissions are required.

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: a clear one-liner, followed by context about the entity, then argument details. It is slightly lengthy but each section adds value. Front-loads the core purpose well.

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 presence of an output schema (true) and the tool's complexity, the description is complete. It explains the return value, provides a query example to find confirmations, and covers all arguments. No major gaps.

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?

The input schema has 0% description coverage, but the description compensates fully. It explains confirmation_id (can be confirmation or sales order ID), legal_entity (company code), save_path (optional full path), and profile (default), with examples. This adds significant semantic value beyond the 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 sales confirmation report as a PDF from D365 F&O. It specifies the resource (sales confirmation) and the action (download PDF), and distinguishes from siblings like d365fo_download_customer_invoice by noting it uses SalesConfirmController.

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 guidance on when to use the tool (for downloading sales confirmations) and how to find available confirmations via querying the SalesOrderConfirmationHeader entity with an example. It does not explicitly state when not to use it, but the context among sibling download tools implies it's for sales confirmations.

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