appwrite_list_functions

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

No annotations provided, so description carries full burden. States 'List all' implying read-only, but fails to disclose pagination behavior, return structure, or filtering capabilities (despite having query/search parameters). No mention of auth requirements or rate limits.

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 description is appropriately brief. However, the '[UNIFIED]' prefix appears to be metadata noise that doesn't aid tool selection. No redundancy or fluff in the substantive content.

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?

No output schema exists, yet description doesn't explain return values or structure. With 0% parameter schema coverage and no annotations, the description inadequately covers the 3-parameter input contract for a listing operation in a complex platform.

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 has 0% description coverage for 3 parameters (site, queries, search). Description completely omits parameter explanation, failing to compensate for undocumented schema. Required 'site' parameter is unexplained (ID vs name), and filtering parameters (queries, search) lack syntax guidance.

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 specific verb (List) and resource (serverless functions), providing clear purpose. However, lacks differentiation from sibling `appwrite_get_function` (single retrieve vs listing) and the "[UNIFIED]" prefix adds noise without clarifying scope.

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 `appwrite_get_function` or `appwrite_list_deployments`. No mention of filtering capabilities despite `queries` and `search` parameters existing in schema.

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