Dataverse 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 of behavioral disclosure. It mentions that the tool 'creates visual documentation' and saves a file, implying a write operation, but does not specify file format details (e.g., .mmd), potential side effects, permissions required, or error handling. For a tool with no annotations and file output, this leaves significant gaps in understanding its behavior.

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 front-loaded with the core purpose in the first sentence, followed by additional context. It consists of only two sentences with zero waste, efficiently conveying the tool's value without unnecessary elaboration.

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 (generating diagrams from JSON files), no annotations, and no output schema, the description is minimally adequate. It covers the purpose and usage context but lacks details on output format, error conditions, or dependencies. For a tool with 5 parameters and file generation, more completeness would be beneficial.

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 100%, so the schema already documents all 5 parameters thoroughly. The description adds no additional parameter semantics beyond what the schema provides, such as explaining the relationship between schemaPath and the JSON structure. Baseline 3 is appropriate when the schema does the heavy lifting.

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: 'Generates a Mermaid entity relationship diagram from an exported schema JSON file.' It specifies the verb ('generates'), resource ('Mermaid entity relationship diagram'), and source ('exported schema JSON file'). It distinguishes from siblings by focusing on diagram generation rather than data operations like create, update, or delete.

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 for when to use this tool: 'Perfect for documentation, presentations, and understanding data structure.' It implies usage for visual documentation purposes. However, it does not explicitly state when not to use it or name specific alternatives among siblings, such as export_solution_schema for raw schema export.

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