describe_db_instance_net_info

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

The description confirms the read-only nature (consistent with readOnlyHint) and specifies batch behavior, but does not disclose additional traits such as authentication needs or rate limits, which are not covered by annotations.

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 concise with a clear structure (purpose, Args, Returns), but could be more informative without increasing length; each sentence is valuable.

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?

Given the tool's simplicity (2 simple params, no enums, output schema exists), the description is complete enough for a read-only batch retrieval, though it omits error handling or edge cases.

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 compensate; it provides an example for 'db_instance_ids', adding marginal value beyond the schema, but does not explain parameter semantics or constraints in depth.

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 retrieves network configuration details for multiple RDS instances in a batch, using a specific verb and resource, and distinguishes from sibling tools like 'describe_db_instances'.

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 is provided on when to use this tool versus alternatives like 'describe_db_instances' or other describe tools; the description does not mention context or exclusions.

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