appwrite_delete_deployment

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

No annotations are provided, so the description carries full disclosure burden. It fails to mention this is destructive/permanent, lacks information on auth requirements, side effects (e.g., what happens if deleting an active deployment), or return values.

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?

While brief, the '[UNIFIED]' prefix is structural noise/metadata leakage. The single sentence is tautological (restates the tool name) and underspecified rather than elegantly concise—every sentence does NOT earn its place due to lack of information density.

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 operation with 3 required parameters, zero schema coverage, and no output schema, the description is seriously incomplete. It offers no warning about data loss, no parameter documentation, and no indication of success/failure handling.

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% with no descriptions for 'site', 'function_id', or 'deployment_id'. The description adds no parameter context, leaving the agent unaware that this requires a composite identifier (site + function + deployment) or what 'site' refers to in the Appwrite context.

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 states the core action ('Delete') and resource ('deployment'), but includes metadata noise ('[UNIFIED]'). It fails to clarify that this targets function deployments specifically (evident only from parameters) and doesn't distinguish nuances from sibling tools like appwrite_activate_deployment.

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 provided on when to use versus alternatives, prerequisites (e.g., needing the function_id), or warnings about destructive behavior. The agent receives no signal about irreversibility or dependencies.

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