create_database

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

The description merely restates the action and does not disclose any side effects, permissions, or failure modes beyond what the annotations already indicate (readOnly=false). No additional behavioral context is provided.

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 concise sentence that conveys the primary purpose without superfluous text, though it lacks substance. The phrasing is efficient but under-specified.

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?

The description is severely incomplete for a tool with four parameters and no output schema. It does not describe the required inputs, expected result, or any prerequisites beyond API support, leaving the agent without essential information.

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 should explain the parameters, but it does not mention name, host, server_id, or connections_from. The agent must infer their meanings solely from parameter names, which is insufficient.

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 uses the specific verb 'Create' and the resource 'database', clearly distinguishing it from sibling database tools like list_databases and delete_database. The conditional clause about Wisp Client API adds context without obscuring the core purpose.

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 offers no guidance on when to use this tool versus alternatives, aside from the precondition about API support. It does not mention using list_databases to verify existing databases or any fallback options.

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