Bulk Create/Update Service Environment Variables

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

Description adds value beyond annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by explaining upsert behavior, audit logging for reveal parameter, and instance safety note to prevent accidental prod writes. Missing details on rate limits or error handling, but overall strong.

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?

Three concise sentences, front-loaded with main action, no wasted words. Every sentence provides critical context.

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 bulk update tool with full schema coverage. Covers upsert semantics, scope restriction, instance safety, and audit note. Lacks response format or error handling details, but not critical given no output schema.

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 100%, but description adds significant meaning: upsert behavior for variables, instance parameter explained with explicit safety rationale, and reveal parameter noted as audited. This goes beyond raw schema descriptions.

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 verb 'Create or update' and resource 'multiple environment variables at once for a Coolify service (docker-compose apps)', distinguishing it from sibling tools like coolify_create_app_env or coolify_update_service_env by emphasizing bulk/upsert behavior and Flavor C app scope.

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?

Explicitly states 'Use for Flavor C apps (ContactHub, CRM, etc.) — NOT for single-container applications', providing clear context for when to use vs avoid. Does not name specific alternative tools but context from sibling list implies singular env var tools exist.

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