instance_create

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

No annotations provided. The description only mentions creation but does not disclose any behavioral traits like permissions, idempotency, side effects, or potential impacts. For a tool with no annotation coverage, this is insufficient.

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-line action followed by a clean Args list. Every sentence serves a purpose with no redundancy. It is well-structured and easy to scan.

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 7 parameters and no output schema, the description lacks context on return values, effects, or how this operation fits into the broader workflow. It does not explain what constitutes a 'database instance configuration' or any post-creation steps.

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 0%, but the description adds Chinese comments for each parameter (e.g., '实例名称' for instance_name, 'master/slave' for type). This provides basic semantics beyond the schema titles. However, it does not explain formats, constraints, or relationships between 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 clearly states the action '创建新的数据库实例配置' (create new database instance configuration) with a specific verb and resource. It distinguishes from sibling tools like instance_update and instance_delete by focusing on creation. The parameter list further clarifies the scope.

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 on when to use this tool vs alternatives such as instance_update or instance_delete. Missing prerequisites, context, or when-not-to-use scenarios. The description only states what the tool does, not when to use it.

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