d365fo_download_purchase_order

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

No annotations are provided, so the description must fully disclose behavior. It mentions the tool downloads a PDF and can auto-generate save_path, but it does not state whether the operation is read-only, destructive, or requires permissions. For a download tool, it likely is read-only, but the lack of explicit disclosure reduces transparency.

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 a clear introduction, contextual explanation of purchase orders, actionable query instructions, and parameter list. While slightly verbose with the definition of purchase orders, it remains focused and front-loaded. It could be trimmed but is not overly long.

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 and an output schema, the description covers the tool's purpose, parameter details, return value, and provides a concrete query example to aid input preparation. It lacks error handling or permission details, but for a download tool, the coverage is adequate.

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, meaning no parameter descriptions in the schema. The description compensates fully by listing all four parameters in an Args section with meanings, examples (e.g., purchase_order_id: 'PO-000123'), and default values (profile: 'default'). It adds crucial context 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 'Download a purchase order report as PDF from D365 Finance & Operations.' It uses a specific verb ('download') and resource ('purchase order'), and even mentions the underlying controller (PurchPurchaseOrderController). This makes the tool's purpose distinct from siblings like d365fo_download_customer_invoice, though not explicitly compared.

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 how to find purchase orders via a query (e.g., using d365fo_query_entities with entity 'PurchaseOrderConfirmationHeaders'), which helps the agent prepare input. However, it does not explicitly state when to use this tool versus alternatives like d365fo_download_customer_invoice or when not to use it.

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