Dynamics 365 Finance & Operations MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: the tool performs a destructive deletion operation and automatically invalidates cached connections. It also hints at the return format. However, it lacks details on permissions, error handling, or rate limits, which would be helpful for a mutation 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?

The description is well-structured and front-loaded with the core action, followed by behavioral consequences and parameter/return details. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 (a destructive operation with side effects), no annotations, and an output schema present, the description is mostly complete. It covers purpose, behavior, parameters, and returns. However, for a deletion tool, additional context like prerequisites or irreversible consequences would enhance 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?

Schema description coverage is 0%, so the description must compensate. It adds meaning by specifying that 'profileName' is the 'Name of the profile to delete', which clarifies the parameter's purpose beyond the schema's basic type information. Since there is only one parameter, this is sufficient, but it does not provide format examples or constraints.

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 specific action ('Delete') and resource ('D365FO environment profile'), distinguishing it from sibling tools like 'd365fo_clone_profile', 'd365fo_create_profile', 'd365fo_update_profile', and 'd365fo_validate_profile'. It precisely identifies what the tool does without ambiguity.

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 clear context by mentioning that deletion 'automatically invalidates all cached client connections', which implies when to use it (to remove a profile and disconnect clients). However, it does not explicitly state when not to use it or name alternatives like 'd365fo_update_profile' for modifications instead of deletion.

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