List Lucky security groups

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

Annotations already establish safety/read-only behavior, and the description adds concrete behavioral context by stating that passwords are redacted in output. This is useful beyond the annotations; no contradiction exists.

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 core statement is concise and front-loaded. The second sentence about creating users adds a useful limitation but is slightly tangential to the tool's own invocation.

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 parameterless list operation with strong annotations, the description is essentially complete: it names the listed entities and the important redaction behavior. No output schema exists, but the expected return content is summarized well enough for a simple list.

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 zero parameters and 100% schema coverage, so there is no undocumented parameter burden. Per the baseline for parameterless tools, the description does not need to add parameter detail.

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 uses a clear verb+resource combination: 'List security groups, grants, and users.' It also distinguishes the scope from the many sibling list tools by naming exactly what entities are returned. The title and description agree without being a tautology.

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 list operation and resource naming make the primary use case obvious, but there is no explicit when-to-use guidance or comparison with sibling tools. The note that creating users with passwords is not exposed hints at a non-goal but stops short of naming an alternative.

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