appwrite_delete_subscriber

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

No annotations provided, so description carries full burden. 'Remove' implies destructive behavior but doesn't clarify if permanent/hard-delete, reversible, or if it triggers side effects like notifications. Lacks auth or rate limit context required for delete operations.

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?

Single sentence, appropriately brief. Front-loaded with action verb. '[UNIFIED]' tag appears to be metadata leakage that doesn't serve the agent, slightly reducing structural quality.

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?

For a destructive 3-parameter operation with no annotations and no output schema, the description is insufficient. Missing parameter details, error conditions, and scope limitations expected for this complexity level.

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 only implicitly references 'topic' and 'subscriber' but doesn't explain the 'site' parameter, ID formats, or that all three parameters are required identifiers. Fails to compensate for undocumented schema.

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?

Clear verb ('Remove') and resource ('subscriber') with scope ('from a topic'). Distinguishes from sibling create_subscriber and delete_topic operations. '[UNIFIED]' prefix is noise but doesn't obscure clarity.

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 explicit guidance on when to use versus alternatives, prerequisites (e.g., needing valid topic/subscriber IDs), or preconditions. Only states what the tool does, not when to choose it.

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