appwrite_get_function

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 but only states what data is returned. It fails to mention error handling (e.g., invalid function_id), authentication requirements, or whether this is a read-only operation.

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 a single sentence and brief, but it is front-loaded with the '[UNIFIED]' metadata tag which serves no semantic purpose for tool selection and constitutes noise.

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 zero schema descriptions, no annotations, and no output schema, the description is insufficient. It hints at the return value but completely omits parameter semantics and operational constraints necessary for a 2-parameter GET operation.

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?

The input schema has 0% description coverage, and the description offers no parameter clarification. While 'function_id' is somewhat inferable from context, the 'site' parameter is ambiguous (site ID, name, or URL?) and requires description-level documentation that is absent.

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 retrieves function details using the specific verb 'Get' and enumerates what is returned (deployment status and configuration). However, it does not distinguish from sibling tools like appwrite_get_deployment or appwrite_get_active_deployment, which also handle deployment-related data.

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 such as appwrite_list_functions or appwrite_get_deployment. There are no prerequisites, filters, or contextual triggers mentioned.

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