get_address_configuration

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

With no annotations provided, the description carries responsibility for behavioral disclosure. It only states 'Get detailed configuration,' which implies a read operation but says nothing about permissions, error behavior, or response structure. It adds little beyond what the name already conveys.

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 one concise sentence and easily digestible, but it largely paraphrases the tool name, offering only the word 'static IP address' as additional context.

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 tool with one parameter and no output schema, the description gives only the core purpose. It lacks behavioral details, parameter guidance, and return value explanation, making it minimally complete.

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 a single address_id parameter with 0% description coverage. The description's reference to 'a specific static IP address' hints that address_id identifies the IP, but it does not explain the format, where to find it, or any constraints.

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 specific verb 'Get' and identifies the exact resource ('detailed configuration of a specific static IP address'), clearly distinguishing it from sibling get_*_configuration tools by naming the resource type.

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 implies usage for retrieving configuration of a specific IP address, but it does not provide explicit when-to-use guidance, alternatives, or exclusions. It does not mention that list_vpc_addresses could be used to find address_id, for example.

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