d365fo_query_entities

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

With no annotations, the description carries full burden. It describes the query behavior, simplified OData filtering, and return format (dictionary with data, count, pagination). It does not mention auth or rate limits, but such details are less critical for a read-only query tool.

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?

Description is well-structured with Args, Returns, and Note sections. It is informative without being overly verbose. Minor redundancy in explaining filter patterns could be tightened, but overall efficient.

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 no output schema, description adequately explains return type. All 9 parameters are documented, including complicated filter syntax. Missing some edge cases like error handling, but for a query tool this is sufficient.

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 coverage is 0%, so description must compensate. It thoroughly explains each parameter, especially filter with detailed examples of wildcard patterns and enum values. This provides far more meaning than the schema alone.

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?

Description clearly states it queries D365FO data entities with simplified filtering. It distinguishes from siblings like d365fo_get_entity_record (single record) and d365fo_create_entity_record (creation) by focusing on querying multiple entities with filtering and pagination.

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?

Explicitly notes that only 'eq' operations with wildcards are supported, and advises to retrieve data first and filter programmatically for complex queries. This provides clear when-not-to-use guidance, though it does not explicitly compare to sibling tools.

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