appwrite_create_team_membership

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Invite' implies sending a notification, the description fails to disclose critical behavioral details: whether invitations expire, if acceptance is required, what the `url` parameter controls (callback URL), or side effects like email/SMS delivery.

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 concise with two focused sentences. However, the '[UNIFIED]' prefix appears to be metadata cruft that does not add value to the agent, slightly detracting from an otherwise efficient structure.

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 8 parameters with 0% schema coverage, no output schema, and no annotations, the description is insufficient for a complex invitation workflow. It omits explanation of the invitation lifecycle, the purpose of half the parameters, and expected outcomes, leaving significant gaps in contextual understanding.

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 description coverage is 0%, requiring the description to compensate. The text only partially explains three parameters (email, phone, user_id) by listing them as invitation methods. Critical parameters like `site` (purpose unclear), `roles` (array content undefined), `url`, and `name` receive no semantic explanation, leaving the majority of the schema 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 specific action (invite) and resource (team membership) and distinguishes the three possible identification methods (email, phone, user ID). However, it does not explicitly differentiate from sibling tools like `appwrite_update_membership` or clarify that this creates a new membership record versus updating existing ones.

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 implies the flexibility of invitation methods (email, phone, or user ID), suggesting these are alternatives, but lacks explicit guidance on when to use which method, prerequisites for the invitee, or what happens if the user is already a member. No explicit alternatives or exclusions are stated.

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