Dynamics 365 Finance & Operations MCP Server

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: the tool cancels sessions, requires sessions to be 'currently running and marked as cancellable', and returns a 'Dictionary with cancellation result'. However, it lacks details on permissions, error handling, or side effects, which are important for a cancellation operation. The description adds value but is not comprehensive.

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 purpose, followed by concise sections for Args and Returns. Every sentence earns its place by providing essential information without redundancy, making it easy to parse and understand quickly.

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 (cancellation operation with no annotations and no output schema), the description is reasonably complete. It covers purpose, usage conditions, parameters, and return type. However, it lacks details on error cases or the structure of the return dictionary, which could be important for agent handling. It's adequate but has minor gaps.

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 explains both parameters: 'session_id' as 'Session ID of the sync operation to cancel' and 'profile' as 'Configuration profile to use (optional - uses default profile if not specified)'. This adds clear meaning beyond the schema's basic types, though it doesn't detail format or constraints for 'session_id'.

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 ('Cancel a running sync session') and resource ('sync session'), distinguishing it from siblings like 'd365fo_start_sync' (which initiates sync) and 'd365fo_get_sync_progress' (which monitors sync). It precisely defines what the tool does without being vague or tautological.

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 explicitly states when to use this tool ('Only sessions that are currently running and marked as cancellable can be cancelled'), providing clear usage criteria. It also implies alternatives by specifying the conditions, helping the agent decide when this tool is appropriate versus other sync-related tools like checking progress or history.

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