appwrite_search_documents

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

No annotations provided, so description carries full burden. Only discloses the index prerequisite. Omits search syntax details (wildcard, fuzzy), case sensitivity, pagination behavior, and error modes when the index is missing.

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?

Two sentences with minimal waste, though the '[UNIFIED]' prefix at the start is structural noise that doesn't assist tool selection and could be removed.

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 a 6-parameter database tool with 0% schema coverage and no output schema. Missing explanations for the site/database/collection hierarchy and return value structure.

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. Description mentions 'searched attribute' giving context to the 'attribute' parameter, but leaves 5 other parameters (site hierarchy, database_id, collection_id, query format, limit) completely unexplained.

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 'Full-text search in documents' with specific verb and resource. Distinguishes from siblings list_documents and get_document by specifying 'full-text', though the '[UNIFIED]' prefix adds metadata noise without value.

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 critical prerequisite 'Requires a fulltext index', but fails to distinguish when to use this versus list_documents or get_documents_by_ids for document retrieval scenarios.

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