appwrite_health_db

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

No annotations provided, so description carries full burden. Discloses return values ('ping time and connection status') implying read-only behavior, but omits rate limits, authentication requirements, or side effects.

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, front-loaded with purpose. '[UNIFIED]' prefix is minor noise but doesn't significantly detract. Every sentence conveys meaningful information about function or return value.

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?

Adequate for a simple health endpoint given return values are described (compensating for missing output schema), but incomplete due to undocumented required parameter. Meets minimum viability but has clear 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 coverage is 0% for the required 'site' parameter, and description fails to compensate by explaining what 'site' means (URL, ID, or name) or providing examples. Critical documentation gap for a required parameter.

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?

Specific verb 'Check' + resource 'database health status' + return value details ('ping time and connection status'). Clearly distinguishes from sibling health tools (health_cache, health_storage, etc.) by specifying 'database'.

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 on when to use this versus other health endpoints (appwrite_health_check, appwrite_health_cache, etc.) or prerequisites. Lacks explicit when-not-to-use or alternative suggestions.

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