appwrite_update_team

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

No annotations provided, yet the description discloses almost no behavioral traits. It does not specify what happens if the team_id doesn't exist, whether the update is partial or full, or what constitutes a successful response.

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 extremely brief (5 words excluding the bracketed prefix), which is efficient but insufficient given the lack of structured metadata. The '[UNIFIED]' tag appears to be implementation metadata that clutters the description without aiding the agent.

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 mutation tool with three undocumented parameters, no annotations, and no output schema, the description is inadequate. It fails to explain the Appwrite-specific context of 'teams' or describe the operation's side effects and return behavior.

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% with no descriptions for 'site', 'team_id', or 'name' in the JSON schema. The description only implicitly hints that the 'name' parameter accepts the new team name, but offers no explanation for 'site' (Appwrite project/site?) or expected format for 'team_id', failing to compensate for the schema's lack of documentation.

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?

Description states the basic operation (updating a team name) with a clear verb and resource. However, it provides no differentiation from sibling tools like `appwrite_update_membership` or `appwrite_create_team` beyond the implied CRUD operation. The '[UNIFIED]' prefix appears to be metadata leakage that adds no semantic value.

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?

Contains no guidance on when to use this tool versus alternatives like `appwrite_create_team` or when the team must already exist. No prerequisites are mentioned despite requiring a valid `team_id`.

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