d365fo_create_profile

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains the credential source options and basic operation, but omits side effects (e.g., whether the profile becomes active immediately), required permissions, error behavior, or the structure of the return dictionary. For a tool with no annotations, this level of transparency is adequate but not exhaustive.

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 an Args list and Returns section, making it easy to scan. However, it is lengthy and repeats some default values already in the schema. Each sentence is justified, but some redundancy could be trimmed. The front-loading of the main purpose is effective.

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 complexity (13 parameters, credential configuration) and the existence of an output schema, the description covers inputs well but lacks detail on the output beyond 'Dictionary with creation result'. It does not address error scenarios, prerequisites (e.g., authentication), or post-creation state. For a tool creating a critical resource, more contextual completeness is warranted.

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 zero description coverage, leaving the description to fully document each parameter. The Args section thoroughly explains all 13 parameters, including defaults, types, and optionality. Notably, it provides detailed structure for the complex 'credentialSource' parameter, offering concrete examples of environment variable and Key Vault configurations. This adds exceptional value 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 verb 'Create' and the resource 'a new D365FO environment profile'. It distinguishes this tool from sibling tools like clone_profile, delete_profile, etc. by specifying 'full configuration options', emphasizing its role as the primary creation tool.

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 does not provide explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, scenarios where other tools (e.g., clone_profile) might be more appropriate, or any limitations. The implicit naming is insufficient for an agent to make informed decisions without additional context.

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