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

With no annotations provided, the description carries the behavioral burden. It discloses that the tool triggers an export, waits for completion, and then returns a download URL, which communicates the asynchronous/polling nature. It does not discuss side effects like staging reuse or failure behavior, but the main operational behavior is clear.

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 compact and front-loaded with the primary action, then adds a prerequisite note and a clear alternative. Every sentence earns its place, and there is no redundant repetition of schema information.

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?

The description gives the core output (download URL), the prerequisite project setup, and the routing alternative, which is strong for a 5-parameter tool with no output schema. It could additionally note failure/timeout outcomes, but the parameter schema already covers pollTimeoutSeconds, so the overall picture is sufficiently complete.

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 100%, so all five parameters are already documented with meaningful descriptions. The tool description adds high-level context about definitionGroupId being an existing DMF project, but does not need to repeat parameter details because the schema already handles them.

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 triggers a bulk export via the Data Management package REST API and returns a download URL when complete. It distinguishes itself from related tools by emphasizing the project-based export path and explicitly naming odata_export_entity as the alternative for ad-hoc exports.

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 gives explicit when-to-use guidance: use this when a DMF export project already exists. It also says to create the project with dmf_create_data_project if needed, and to use odata_export_entity for ad-hoc exports without a project. This leaves little ambiguity about tool selection.

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