appwrite_list_users

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

No annotations provided, and description fails to disclose return format, pagination behavior, rate limits, or authentication requirements. '[UNIFIED]' prefix is unexplained behavioral metadata that creates confusion without adding clarity.

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 is efficiently structured, but '[UNIFIED]' prefix appears to be implementation metadata that wastes space without aiding tool selection. Content is front-loaded but insufficient for the information gaps present.

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, and no output schema, the description must carry full documentation burden but fails to explain return values, parameter formats, or error behaviors. Inadequate 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?

Schema coverage is 0%, requiring heavy description compensation, but the description only vaguely mentions 'filtering and search' without explaining parameter semantics. Critical required parameter 'site' is undocumented, and query/search format (string structure, syntax) is unspecified.

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 clear verb+resource: 'List all users in the project'. Distinguishes from sibling 'appwrite_get_user' by emphasizing 'all' vs implied single retrieval, though could explicitly contrast with the singular get variant.

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?

No guidance on when to use this versus 'appwrite_get_user' or 'appwrite_search_documents'. No mention of prerequisites, permissions, or filtering syntax recommendations.

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