appwrite_create_boolean_attribute

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a write operation, the description fails to disclose idempotency behavior, error handling (what happens if the key exists), or the effect of the default/required/array parameters on schema constraints.

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 concise at one sentence, but the '[UNIFIED]' prefix appears to be metadata cruft rather than useful content. The brevity is appropriate if there were annotations, but given the complexity (7 params, 0% coverage), this is under-specification disguised as conciseness.

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 schema mutation tool with 7 parameters, zero schema descriptions, no annotations, and no output schema declaration, the description is materially incomplete. It fails to explain the relationship between database_id, collection_id, and key, or what constitutes valid boolean attribute configuration.

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?

With 0% schema description coverage across 7 parameters, the description must compensate but provides no parameter guidance whatsoever. Critical ambiguities remain unexplained: particularly that 'default' accepts string (not boolean) types, that 'array' determines if this is an array of booleans, and what 'site' refers to in the Appwrite context.

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?

The description clearly states the specific action (Create) and target resource (boolean attribute in a collection), distinguishing it from sibling attribute creation tools like appwrite_create_string_attribute and appwrite_create_integer_attribute. It loses a point for the mysterious '[UNIFIED]' prefix and not clarifying that 'attribute' means a database schema field.

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?

The description provides no guidance on when to use this specific tool versus other attribute types, nor does it mention prerequisites (e.g., that a collection must exist first) or whether this operation can be safely retried if the attribute already exists.

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