appwrite_create_database

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

No annotations are provided, so the description carries full disclosure burden. It explains the unique ID auto-generation behavior, but omits critical mutation context such as permissions required, idempotency guarantees, what happens if the database_id already exists, or return value structure.

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?

Two sentences, front-loaded with the core purpose. The second sentence provides actionable value without verbosity. The leading '[UNIFIED]' tag is structural noise, but otherwise efficient.

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 0% schema coverage, no annotations, no output schema, and a 4-parameter mutation tool, the description is incomplete. It covers the create action and one parameter trick, but fails to document 3/4 parameters or mutation side-effects expected for a database creation operation.

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 across 4 parameters, the description must compensate significantly. It provides crucial semantics for database_id (the 'unique()' special value), but leaves 'site', 'name', and 'enabled' entirely undocumented and mysterious.

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 'Create a new database' with a specific verb and resource, distinguishing it from sibling tools like appwrite_get_database or appwrite_update_database. The '[UNIFIED]' prefix is noise but doesn't obscure the purpose. It lacks explicit platform mention (Appwrite), though implied by the tool name.

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?

Provides a specific parameter usage tip ('Use unique() as database_id'), but lacks explicit guidance on when to use this tool versus alternatives like appwrite_update_database or when not to use it (e.g., if database already exists).

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