appwrite_delete_index

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

No annotations provided, so description must carry full burden. While 'Delete' implies destruction, it fails to disclose that this is irreversible, whether it requires specific permissions, impacts on active queries, or what constitutes success/failure.

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 actual content is concise (one sentence), but the '[UNIFIED]' prefix appears to be implementation metadata leaking into the description, creating structural noise without adding value.

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?

For a destructive database operation with 4 undocumented parameters and no output schema, the description is dangerously minimal. Lacks warnings about production impacts, parameter explanations, or return value documentation.

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 has 0% description coverage for all 4 required parameters (site, database_id, collection_id, key). The description fails to compensate by explaining what 'key' refers to (index key vs ID), what 'site' means in this context, or the hierarchy of database→collection→index.

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 the specific action (Delete) and resource (index from a collection). The '[UNIFIED]' prefix is metadata noise that slightly obscures clarity, but the core intent is clear. Distinguishes from siblings like appwrite_create_index by specifying 'Delete'.

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 versus alternatives (e.g., appwrite_list_indexes to verify existence first), no prerequisites mentioned, and no warnings about the implications of index deletion on query performance.

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