appwrite_get_database

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

No annotations provided, so description carries full burden of behavioral disclosure. It fails to indicate this is a read-only operation, does not describe error handling (e.g., 404 if ID not found), return format, or required permissions/authorization for the Appwrite platform.

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?

Single sentence with efficient structure, but includes '[UNIFIED]' prefix that appears to be metadata noise or categorization without explanation, reducing clarity. Otherwise appropriately sized for a simple retrieval tool.

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?

With zero schema descriptions and no output schema, the description should document parameters and expected returns. It fails to explain the 'site' parameter, return value structure, or Appwrite-specific context (e.g., project scope), leaving significant gaps for an API tool.

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%, requiring the description to compensate. It only implicitly references 'database_id' via 'by ID' but provides no explanation for the 'site' parameter (e.g., whether it's a site ID, URL, or subdomain), leaving both parameters effectively undocumented.

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?

States specific verb ('Get') and resource ('database details'), and mentions 'by ID' which implicitly distinguishes from sibling appwrite_list_databases. However, it does not explicitly differentiate from other CRUD siblings (create_database, update_database, delete_database) nor explain the [UNIFIED] tag.

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 no guidance on when to use this tool versus alternatives like appwrite_list_databases (for listing) or appwrite_create_database. Contains no 'when-not' conditions or prerequisite checks (e.g., verifying database existence).

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