d365fo_search_enumerations

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

The description explains the search behavior: simple text matching, not regex, and a multi-step strategy. It also specifies the return type (dictionary of enumerations). Since no annotations are provided, the description carries the full burden and does so effectively, though it does not mention potential errors or rate limits.

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 bolded sections (IMPORTANT, SEARCH STRATEGY EXAMPLES, Args, Returns). It is front-loaded with the purpose, and every sentence adds value, including concrete examples that illustrate the search strategy. Despite its length, it is 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 the tool's complexity (multi-keyword search strategy), no output schema, and no annotations, the description covers purpose, parameters, usage strategy, and return type thoroughly. It could mention error handling or edge cases, but overall it is sufficiently complete for an AI agent.

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?

With 0% schema description coverage, the description greatly expands on each parameter. It clarifies 'pattern' must be plain text keywords (not regex) and provides step-by-step usage examples. 'Limit' and 'profile' are also explained, adding 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 the tool searches for enumerations using simple keyword-based search, specifying it is for D365 F&O. This distinguishes it from sibling search tools like d365fo_search_actions and d365fo_search_entities by explicitly targeting enums.

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 detailed guidance on how to use the tool (break queries into keywords, perform multiple searches), but does not explicitly compare it to alternatives or state when not to use it. The usage is implicit: use when enumerations are needed.

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