appwrite_update_user_labels

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

No annotations provided, so description carries full burden. 'Set' implies mutation but doesn't clarify if this replaces existing labels or appends, nor does it mention authentication requirements, error cases (e.g., invalid user_id), or prerequisites.

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 efficient sentences with zero redundancy. '[UNIFIED]' prefix is unnecessary metadata but doesn't severely impact readability. Information is front-loaded effectively.

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 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It explains the 'why' (permission management) but omits technical details for 2 of 3 parameters and lacks mutation semantics (destructive vs additive).

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?

Critical gap: schema has 0% description coverage. Description mentions 'labels' conceptually but doesn't document the parameter structure (array of strings vs objects), nor does it explain 'site' (URL? ID?) or 'user_id' (Appwrite internal ID? format?).

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?

Clear verb 'Set' and resource 'user labels' with specific context 'for permission management'. Distinguishes from sibling update_user_* tools by specifying labels, though doesn't explicitly map the relationship to other user attribute updates.

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 usage context via example 'label:admin' showing how labels integrate into permission strings. Lacks explicit when-not-to-use guidance or comparison to alternatives like appwrite_update_user_status or appwrite_create_user.

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