MCP Server for OpenMetadata

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

No annotations are provided, so the description carries the full burden. 'Create' implies a mutation, but it doesn't disclose behavioral traits such as required permissions, whether the operation is idempotent, what happens on conflicts, or any rate limits. This leaves significant gaps for a tool that modifies state.

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 a single, clear sentence with no wasted words. It's front-loaded and appropriately sized for the minimal information it conveys, making it efficient to parse.

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 of a creation tool with no annotations, 1 parameter (a nested object) at 0% schema coverage, and no output schema, the description is incomplete. It doesn't address parameter details, behavioral context, or expected outcomes, leaving the agent under-informed for proper tool invocation.

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 schema has 1 parameter with 0% description coverage, and the tool description adds no information about 'service_data'. It doesn't explain what this object should contain, its structure, or required fields, failing to compensate for the lack of schema 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 states the verb 'create' and resource 'messaging service', which provides a basic purpose. However, it's vague about what a 'messaging service' entails and doesn't differentiate from sibling tools like 'create_database_service' or 'create_dashboard_service', leaving the agent to infer the specific domain from the name alone.

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 doesn't mention prerequisites, context, or exclusions, and with siblings like 'list_messaging_services' and 'get_messaging_service', there's no indication of when creation is appropriate versus retrieval.

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