appwrite_delete_attribute

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

With no annotations provided, the description carries the full burden. It successfully discloses the destructive scope (removes field from all documents), but lacks information on reversibility, required permissions, failure modes, or whether the operation succeeds if documents exist.

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 appropriately brief with two efficient sentences. The '[UNIFIED]' prefix is minor noise, but the content is front-loaded with the action followed by critical consequence, earning its place.

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 schema mutation tool with zero schema documentation and no output schema, the description is incomplete. It omits parameter details, return values, and prerequisites (e.g., admin permissions) that would be necessary for safe invocation.

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 fails to compensate adequately. While 'attribute' implies the 'key' parameter and 'collection' implies 'collection_id', it provides no guidance on 'database_id' or 'site' parameters, leaving half the required parameters 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?

The description clearly states the action (delete) and target (attribute from a collection), distinguishing it from document or collection deletion siblings. The second sentence clarifies the scope of impact (all documents), though it doesn't explicitly differentiate from attribute creation tools.

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 mentions the consequence of deletion (removes field from all documents) but provides no explicit when-to-use guidance, prerequisites, or comparison to alternatives like appwrite_delete_collection or the attribute creation tools.

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