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

Annotations already state readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces this by calling the export transactional and non-destructive. It adds meaningful behavioral detail beyond annotations, including automatic server paging, CSV/JSON return formats, and the absence of a DMF project requirement.

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 and information-dense without being bloated. It leads with the core purpose, then covers key capabilities, output formats, usage conditions, and a critical prerequisite in a compact, readable block.

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?

For a read-only export tool with full parameter documentation and rich annotations, the description provides all necessary operational context: what it exports, how it pages, what formats it returns, when to use it, and what to do before calling it. The lack of an output schema is mitigated by the explicit statement that results are CSV or JSON.

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 the structured schema already documents each parameter. The description adds general context about supported OData features ($select, $filter, $orderby) and paging, but these largely mirror the existing schema descriptions rather than adding new semantic depth, so the baseline score of 3 is appropriate.

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 exports any D365 F&O data entity via OData, naming the action, resource, and mechanism. It also distinguishes itself from DMF-based exports by explicitly saying 'no DMF project required' and positioning it as a universal, live export path.

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 guidance on when to use this tool: 'Use for live/ad-hoc exports and small-to-medium volumes.' It also names the alternative for large bulk exports ('prefer dmf_export_package') and instructs the agent to resolve the entity set name via find_entity_for_table/get_data_entity_info rather than guessing.

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