attach_whitelist_template_to_instance

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

With no annotations, the description should fully disclose behavior. It claims an action ('allocate public connection') that likely does not match the tool's actual behavior. No mention of side effects, safety, or requirements, making it highly misleading.

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 short but contains a confusing mismatch between its stated purpose and the tool name. The Args list is redundant with the schema, and the Returns line is generic.

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?

No output schema is present, so the description should explain the return value. It only says 'dict[str, Any]: The response' which lacks detail. The core function is misrepresented, undermining completeness.

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 0%, so the description must add meaning. It provides a useful hint for template_id ('can be obtained via DescribeAllWhitelistTemplate') but offers no extra context for region_id or db_instance_id beyond repeating their names.

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 says 'allocate db instance public connection' which is inconsistent with the tool name 'attach_whitelist_template_to_instance'. The purpose is vague and misleading; the actual action of attaching a whitelist template is not described.

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?

No guidance on when to use this tool versus alternatives (e.g., describe_instance_linked_whitelist_template). The description simply lists parameters without context on prerequisites or when it's appropriate.

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