appwrite_execute_function

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

No annotations are provided, yet the description fails to disclose critical behavioral traits of function execution: that it runs arbitrary code (security/side effects), incurs compute costs, has timeouts, or returns execution logs/results. The burden falls entirely on the description and it provides nothing.

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?

While brief at one sentence, the '[UNIFIED]' prefix wastes space and the extreme brevity is inappropriate given the complete lack of parameter documentation and safety warnings for a high-impact mutation operation.

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?

Completely inadequate for a complex mutation tool with 7 parameters, 0% schema coverage, no annotations, and no output schema. A tool that triggers arbitrary code execution requires extensive documentation about side effects, return values, and error states, none of which are present.

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% (7 parameters, none described), yet the description offers no compensatory documentation. Critical parameters like 'site' (what format?), 'body' (JSON string?), and 'method' (enum values?) are completely 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?

States the basic action ('Execute') and resource ('function') with a hint of sync behavior ('immediately'), but '[UNIFIED]' appears to be metadata noise. Lacks specificity that this targets Appwrite Cloud Functions specifically, though this is somewhat clear from the tool name prefix.

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 no guidance on when to use this versus listing executions, error handling, or prerequisites such as ensuring the function_id exists. Does not explain when to set async_execution to true versus the default false.

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