get_security_group_details

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates the operation is a read (by use of 'Get'), but does not disclose whether authentication is required, what specific configuration elements are returned, or whether there are any side effects. This is a minimal disclosure.

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 a single concise sentence that gets straight to the point. It has no filler and is easy to scan.

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?

The tool is a simple one-parameter getter, but with no output schema and no annotations, the description should at least clarify what 'configuration' includes. It states the purpose but omits return details, preconditions, and any contrast with sibling list tools. Given the low complexity, a more complete description would be comparatively short.

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 schema has one required parameter, security_group_id, with 0% schema description coverage. The description does not explain the parameter's format, meaning, or how it relates to the security group. The field name is self-explanatory, but the description adds no value beyond the schema.

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 the verb 'Get' with the resource 'security group configuration', clearly indicating a read operation for a specific security group. It distinguishes from the sibling tool 'list_vpc_security_groups' which performs a list operation rather than retrieving details for one group.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention that it should be used after listing security groups, nor does it state any preconditions or exclusions. The only implied context is the verb 'Get', which suggests a detail lookup, but no explicit when or why.

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