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 for behavioral disclosure. It states this is a read operation ('Get') but doesn't mention authentication requirements, rate limits, error conditions, or what happens when a label ID doesn't exist. The description mentions a return format ('Dictionary with label text') but provides no details about structure or possible keys.

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 clear sections (purpose, Args, Returns) and uses bullet-like formatting. Every sentence adds value, though the 'Args:' and 'Returns:' headers could be more integrated. It's appropriately sized for a tool with 3-4 parameters and no output schema.

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?

For a read-only tool with no annotations and no output schema, the description provides adequate coverage of parameters and basic return format. However, it lacks important context about authentication, error handling, and the structure of the returned dictionary. Given the schema's 0% description coverage, the description compensates well but doesn't fully address behavioral aspects.

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 description adds significant value beyond the input schema, which has 0% description coverage. It explains all four parameters (labelId, language, fallbackToEnglish, profile) with clear semantics, including examples ('@SYS1234') and default behaviors. The only gap is that 'fallbackToEnglish' isn't in the schema, but the description documents it thoroughly.

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's purpose with a specific verb ('Get') and resource ('label text by label ID'), making it immediately understandable. It distinguishes from obvious siblings like 'd365fo_get_labels_batch' by focusing on single label retrieval. However, it doesn't explicitly differentiate from other read operations like 'd365fo_get_entity_record' beyond the resource type.

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. It doesn't mention when to prefer batch operations (d365fo_get_labels_batch), whether this is for UI labels versus data labels, or any prerequisites. The only implied usage is retrieving a single label, but this isn't stated explicitly.

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