coolify_create_s3_storage

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

Beyond the annotations (all false, indicating no read-only, idempotent, or destructive hints), the description adds important behavioral context: 'Credentials are never returned or logged,' subject to operation mode policy, and audit logging. These are meaningful security and policy disclosures that the annotations do not convey, though the operation mode policy itself is vague.

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 three concise sentences, each providing distinct value: purpose, security behavior, and audit. No filler or redundancy, and the most essential information is front-loaded in the first sentence.

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 an 8-parameter create tool with no output schema, the description covers key context: purpose, authentication scope, security guarantees, policy constraint, and audit. It does not mention return values or prerequisites beyond authentication, but the essential context for invoking the tool is present and well-integrated.

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 description coverage is 100%, so the input schema already documents all eight parameters. The description adds no parameter-specific detail beyond the schema, and any mention of credentials relates to security rather than parameter semantics. Baseline is 3 because the schema carries the burden.

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 'Create a new S3 storage configuration' with a clear verb and resource, and scopes it to 'the authenticated team.' This distinguishes it from generic storage creation tools in the sibling list, such as coolify_create_storage, and aligns with its S3-specific name.

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 clearly implies this tool is for creating S3 storage configurations, which is sufficient context. However, it does not explicitly name alternatives or state when not to use it, though the sibling list includes closely related tools like coolify_create_storage and coolify_validate_s3_storage. The context is clear, but exclusions are absent.

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