coolify_list_s3_storages

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the valuable behavioral disclosure that 'Credentials are NEVER returned', which is not captured by annotations and is important for security expectations. It also clarifies the team scope.

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?

Two short sentences, front-loaded with the main action, and every phrase adds value. No filler or redundancy.

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 list operation with one optional parameter, the description is largely complete. It covers scope, optional filtering, and the critical security caveat about escaping credentials. No output schema exists, so return value details are not required, though pagination or field details could add richness.

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% and the 'name' parameter already has a clear description ('Filter S3 storages by name (case-insensitive partial match)'). The description merely repeats 'optional name filter' without adding further meaning, so it stays at the baseline 3.

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 'List', the resource 'S3 storages', the scope 'for the authenticated team', and the optional 'name filter'. This distinguishes it from sibling tools like coolify_create_s3_storage or coolify_validate_s3_storage, and the 'S3' qualifier disambiguates from coolify_list_storages.

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 context (authenticated team, optional name filter) but does not explicitly state when to use this tool versus alternatives such as coolify_list_storages or other list tools. There is no mention of when not to use it, so guidance is implied rather than explicit.

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