d365fo_get_enumeration_fields

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 describes the operation as read-only (getting fields) but does not explicitly state it is non-destructive or mention any side effects, authorization needs, or rate limits. The description is adequate but could be more transparent.

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 purpose statement, parameter list, and return value. It is front-loaded with the main action. However, the parameter descriptions could be slightly more concise, and the overall length is reasonable for the complexity.

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 retrieves enumeration fields and has no output schema, the description provides high-level return information but lacks specifics like the structure of the dictionary. For a simple retrieve operation it is mostly adequate, but more detail on the return format would improve completeness.

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?

The input schema has 0% description coverage, so the description must compensate. It provides clear explanations for each parameter: enumeration_name with example, resolve_labels and language with defaults and purpose, and profile as optional. This adds significant meaning 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 retrieves detailed members and values for a specific D365 F&O enumeration. The verb 'get' and resource 'enumeration fields' are specific. It differentiates from sibling tools like d365fo_search_enumerations which searches for enumerations, not their fields.

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 implies usage when needing enumeration details but does not explicitly state when to use this tool versus alternatives. No exclusions or when-not conditions are provided. The parameter description for profile mentions optional use but lacks guidance on when to specify it.

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