Alibaba Cloud RDS OpenAPI MCP Server

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

The annotations indicate readOnlyHint=true, which the description doesn't contradict. The description adds value by specifying this returns 'the sql result' (implying raw SQL output format) and that it operates on a specific RDS instance with region context. However, it doesn't mention potential limitations like result size, execution time, or authentication requirements beyond what the parameters imply. With annotations covering the safety aspect, the description provides useful but incomplete behavioral context.

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 brief but inefficiently structured. It starts with the core function, then has an 'Args:' section that repeats parameter names already in the schema, and a 'Returns:' section that states 'the sql result' without elaboration. While concise, it wastes space on redundant formatting and provides minimal value in the parameter and return sections. The information could be more effectively organized in a single coherent sentence.

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 has readOnlyHint annotation and an output schema exists, the description doesn't need to explain safety or return structure. However, for a database diagnostic tool with 2 parameters at 0% schema coverage, the description should provide more context about what InnoDB status information is returned, typical use cases, and parameter requirements. The current description leaves the agent with insufficient guidance about when and how to use this tool effectively.

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?

With 0% schema description coverage, the description must compensate but provides minimal parameter semantics. It only lists parameter names with basic types ('str') and states they're for 'The ID of the RDS instance' and 'the region id of instance' without explaining format requirements, where to find these IDs, or valid region values. This leaves significant gaps in understanding how to properly use the parameters.

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 tool 'show engine innodb status in db' which indicates it retrieves InnoDB status information from a database instance. However, it's somewhat vague about what specific information is returned and doesn't distinguish this tool from other database monitoring tools like 'describe_db_instance_performance' or 'describe_monitor_metrics' in the sibling list. The purpose is clear but lacks specificity about the output content.

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 what specific InnoDB status information is provided, when this tool is appropriate (e.g., for performance troubleshooting vs. general monitoring), or how it differs from other database monitoring tools in the sibling list like 'describe_db_instance_performance' or 'describe_monitor_metrics'. The agent receives no usage context beyond the basic function.

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