appwrite_create_bucket

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

No annotations provided, yet description offers minimal behavioral disclosure beyond 'Create'. Doesn't clarify idempotency, side effects, permission requirements, or what happens if the bucket_id already exists.

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?

Brief (one sentence), but the '[UNIFIED]' prefix at the start buries the lede with unexplained metadata. Efficient length but poor front-loading of actionable information.

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?

Inadequate for an 11-parameter configuration tool. No output schema exists, yet description doesn't hint at return values, defaults behavior, or the relationship between bucket_id and name parameters.

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?

Critical failure: 0% schema description coverage for 11 parameters including complex fields like 'permissions', 'compression', and 'allowed_file_extensions'. Description completely fails to compensate—mentions zero parameters or their formats/relationships.

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 (Create) and resource (storage bucket), but the '[UNIFIED]' prefix is unexplained noise that doesn't clarify scope. Fails to distinguish from sibling update_bucket or delete_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 update_bucket, list_buckets, or get_bucket. No mention of prerequisites, uniqueness constraints for bucket_id, or error conditions if bucket exists.

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