appwrite_get_document

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

No annotations are provided, so the description carries the full burden of disclosure. It only implies a read-only operation via the verb 'Get' but does not confirm safety, error handling (e.g., document not found), rate limits, 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 text is brief (one sentence), but the '[UNIFIED]' prefix is extraneous metadata. Given the complete lack of schema documentation for five parameters, the description is under-informative rather than efficiently concise.

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?

The tool has five parameters with complex hierarchical relationships (site > database > collection > document) and no output schema. The description fails to explain the hierarchy, the optional `queries` parameter's purpose (projection/filtering), or the return value structure, leaving significant gaps.

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 description coverage is 0%, requiring the description to compensate. It only implicitly addresses `document_id` via 'by ID'. The other four parameters (`site`, `database_id`, `collection_id`, `queries`) are undocumented, including the ambiguous `queries` parameter which is non-obvious for a single-document retrieval endpoint.

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 the specific action (Get) and resource (single document) with the key identifier (by ID), which distinguishes it from plural list operations like `appwrite_list_documents`. However, it does not differentiate from `appwrite_get_documents_by_ids` (batch retrieval) or clarify when to prefer searching over direct ID access.

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 tool versus alternatives such as `appwrite_list_documents`, `appwrite_search_documents`, or `appwrite_get_documents_by_ids`. No prerequisites (e.g., needing valid database/collection IDs) are mentioned.

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