d365fo_download_srs_report

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

No annotations are provided, so the description must disclose behavioral traits. It indicates the tool generates and downloads a PDF, which is a read operation. However, it doesn't mention potential side effects (e.g., report generation triggers), permissions required, limits, or error conditions. Some behavioral context is missing.

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 opening, bulleted parameter list, and a table. It is front-loaded with the core purpose. While lengthy, every sentence adds value, though it could be slightly more concise by removing some redundancy.

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 complexity (8 parameters, 0% schema coverage, no annotations) and the presence of an output schema, the description is remarkably complete. It explains the return value, provides default values, and offers a reference table for common configurations. No significant gaps remain.

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?

Schema description coverage is 0%, but the description fully compensates by detailing each parameter: document_id, legal_entity, controller_name, data_table, data_field, document_type, save_path, and profile. It explains defaults, provides examples, and includes a comprehensive table of common controller/table/field combinations, adding immense value beyond the raw 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 explicitly states it downloads SSRS reports from D365FO as PDF files, listing specific document types (invoices, purchase orders) and the tool's flexibility. The verb 'download' and resource 'SSRS report' are clear, and the tool is distinct from generic data download tools.

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 useful parameter combinations (controller/table/field) but lacks guidance on when to use this generic tool versus the many sibling download tools (e.g., d365fo_download_customer_invoice). No explicit when/when-not or alternative recommendations.

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