coolify_validate_s3_storage

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

The description adds important context by stating 'Audited as a mutation action,' which explains why the readOnlyHint is false. It also mentions the specific API call (ListObjectsV2), providing insight into how the validation is performed. This goes beyond the annotations by clarifying the mutation classification and the underlying mechanism.

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 extremely concise, consisting of only two sentences. It front-loads the core purpose and includes only the essential behavioral note about being a mutation. No words are wasted.

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 simple validation tool with one parameter, the description covers the main purpose and the mutation distinction. However, it does not explain what the response will be (e.g., success indicator, error details) or what the user should expect after invocation. Since there is no output schema, the description could offer more on the outcome, making it minimally complete but with a notable gap.

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?

The input schema has one parameter (s3_storage_uuid) with a complete description ('S3 Storage UUID'), so the schema covers 100% of the parameter semantics. The tool description does not add any additional detail about the parameter, but the schema is sufficient. Baseline score of 3 is appropriate.

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 tool validates an S3 storage connection and specifies the method (ListObjectsV2). It is distinct from sibling tools like coolify_validate_server, which validates a different resource. The verb 'validate' and the resource 'S3 storage connection' are specific and unambiguous.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention any prerequisites, conditions, or refer to similar tools. The usage is only implied: you validate an S3 storage connection when you need to check its connectivity.

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