appwrite_count_documents

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

No annotations provided, so the description carries full burden. It mentions 'optional filters' but fails to disclose if this is a read-only safe operation, what the return format is (integer? object?), performance characteristics with large collections, or authentication requirements.

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 brief (one sentence), but wastes front-loaded space with the '[UNIFIED]' tag that appears to be internal metadata rather than helpful documentation. Otherwise efficiently structured.

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 the description doesn't explain what value is returned (count number, object structure, etc.). With 4 undocumented parameters and no annotations, the description provides insufficient context for proper invocation.

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. The description mentions 'optional filters' which maps to the 'queries' parameter, but provides no semantics for the other 3 parameters (site, database_id, collection_id). With zero schema documentation, the description inadequately compensates by explaining parameter purposes or formats.

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 states a specific verb ('Count') and resource ('documents in a collection') and mentions 'optional filters' which indicates functionality. However, the '[UNIFIED]' prefix is noise that doesn't aid selection, and it could better distinguish from the sibling 'appwrite_list_documents' tool.

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?

No guidance provided on when to use this versus 'appwrite_list_documents' or 'appwrite_search_documents'. Doesn't mention that this returns only a number versus full document data, which is critical for agent decision-making.

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