MCP Server for OpenMetadata

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 but fails to do so. It states 'create' implies a write operation but does not cover permissions, side effects, error handling, or response format. This leaves critical behavioral traits undefined 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 extremely concise with a single sentence, 'Create a new basic test suite', which is front-loaded and wastes no words. However, this brevity comes at the cost of under-specification, but it meets the criteria for conciseness.

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 as a creation tool with no annotations, 0% schema coverage, no output schema, and a nested object parameter, the description is severely incomplete. It lacks details on behavior, parameters, output, and differentiation from siblings, making it inadequate for effective use.

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 input schema has 0% description coverage, with one required parameter 'test_suite_data' of type object. The description adds no information about this parameter's structure, required fields, or semantics, failing to compensate for the schema's lack of documentation.

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 'Create a new basic test suite' restates the tool name with minimal elaboration, making it tautological. It specifies the verb 'create' and resource 'basic test suite' but lacks detail on what a 'basic test suite' entails or how it differs from sibling tools like 'create_executable_test_suite' or 'create_test_case', leaving the purpose vague.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, context, or comparisons to sibling tools such as 'create_executable_test_suite' or 'create_test_case', offering no help for an AI agent in selecting the appropriate tool.

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