appwrite_list_buckets

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

No annotations provided, so description carries full disclosure burden. While 'List' implies read-only safety, the description omits critical Appwrite-specific behaviors: query syntax requirements for the 'queries' parameter, pagination limits, and the scope of 'all' (project-wide vs. user-specific).

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 structure is efficient, though '[UNIFIED]' prefix wastes space without adding actionable information for the agent. Otherwise appropriately sized for what should be a simple listing 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?

Given Appwrite's complex query string syntax and the presence of 'queries'/'search' parameters, the description is inadequate. Without output schema or annotations, it should explain parameter formats, pagination, or link to query syntax documentation.

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% and description fails to compensate. The 'site' parameter (likely Appwrite project/site ID) and 'queries' parameter (which requires specific Appwrite query syntax like 'equal(\"field\", \"value\")') are completely undocumented. The description adds zero semantic value beyond the schema property names.

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 'storage buckets' clearly. The '[UNIFIED]' prefix is unnecessary metadata noise, but the core purpose is specific enough to distinguish from sibling 'appwrite_get_bucket' (single retrieval) and mutation tools like 'appwrite_create_bucket'.

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_bucket' or other storage operations. No mention of pagination behavior, rate limits, or whether this returns all buckets or requires specific permissions.

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