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 full burden but offers minimal behavioral insight. It mentions filtering by credential source but doesn't disclose critical traits like whether this is a read-only operation, potential rate limits, authentication needs, or error conditions. For a search tool with zero annotation coverage, this is inadequate transparency.

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 efficiently structured with a clear purpose statement followed by parameter explanations and return value. Every sentence adds value without redundancy. The Args/Returns formatting enhances readability while maintaining brevity.

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 3 parameters with 0% schema coverage and no annotations, the description does well on parameters but lacks behavioral context. The output schema exists, so return values needn't be detailed. However, for a search tool with credential filtering, more guidance on usage and limitations 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?

Schema description coverage is 0%, so the description must compensate. It successfully explains all three parameters: 'pattern' matches in name/description/URL, 'hasCredentialSource' filters by credential presence, and 'credentialSourceType' filters by type. This adds substantial meaning beyond the bare schema, though it doesn't cover edge cases or examples.

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 ('Search') and resource ('D365FO environment profiles'), making the purpose evident. It distinguishes from siblings like 'd365fo_list_profiles' by specifying search criteria, though it doesn't explicitly contrast them. The description is specific but lacks explicit sibling differentiation for a perfect score.

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 no guidance on when to use this tool versus alternatives like 'd365fo_list_profiles' or 'd365fo_get_profile_names'. It mentions criteria but doesn't explain use cases, prerequisites, or exclusions. This leaves the agent without context for tool selection among similar siblings.

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