appwrite_list_attributes

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to indicate if this is read-only, whether results are paginated, what happens if the collection doesn't exist, or required permissions. The '[UNIFIED]' prefix appears to be metadata rather than behavioral context.

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 (excluding the [UNIFIED] tag). While efficiently worded, it may be overly terse given the complete absence of schema documentation and annotations that would normally provide necessary context.

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 4 parameters with 0% schema coverage, no annotations, and no output schema, the description is insufficient. It fails to explain the resource hierarchy (site → database → collection → attributes) or what constitutes an attribute in this context beyond the parenthetical.

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, the description must compensate but provides no parameter details. It doesn't explain what 'site' refers to (Appwrite instance identifier), expected formats for IDs, or the purpose of the optional 'queries' parameter for filtering attributes.

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 tool 'List[s] all attributes (fields/columns) of a collection,' providing specific verb, resource, and clarifying terminology. However, it lacks explicit differentiation from siblings like appwrite_list_collections or appwrite_create_*_attribute tools, though the resource names differ.

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 tool versus alternatives (e.g., when to use appwrite_get_collection instead), nor does it mention prerequisites like requiring valid database_id and collection_id from prior steps.

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