appwrite_list_team_memberships

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

No annotations provided, so description must carry full burden. Fails to disclose read-only safety, pagination behavior, permission requirements, or response structure. 'List all' suggests unfiltered return, but parameters allow filtering without explanation.

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 front-loaded verb. '[UNIFIED]' prefix wastes tokens without adding value. 'memberships (members)' is slightly redundant but clarifies domain terminology. Appropriately short but arguably under-specified rather than efficiently concise.

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?

Insufficient for a 4-parameter tool with 0% schema coverage and no output schema. Lacks explanation of parameter interactions (how queries/search filter results), output structure (what membership data includes), or relationships to update/delete membership siblings.

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% (no property descriptions), yet description mentions no parameters. Critical parameters like 'site' (Appwrite instance identifier?), 'queries' (query syntax?), and 'search' (searchable fields?) are completely undocumented. Description fails to compensate for schema deficiency.

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 'List' and resource 'memberships (members) of a team'. Distinguishes from sibling appwrite_list_teams (teams vs memberships) and appwrite_create_team_membership (create vs list). Parenthetical clarifies terminology. '[UNIFIED]' prefix is noise but doesn't obscure purpose.

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 explicit guidance on when to use vs alternatives (e.g., appwrite_get_team), prerequisites (team_id must exist), or when not to use (e.g., if you need full user details vs just membership records). Only states what it does, not decision criteria.

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