get_connection_ipv6_config

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

The description lists possible error codes, adding transparency about failure modes. However, without annotations, it fails to disclose more behavioral traits (e.g., it is read-only, but that is implied by 'Returns'). The error list is helpful but basic.

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?

Extremely concise with two sentences. The main purpose is front-loaded, and the error codes are listed separately. No wasted words.

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 description is adequate for a simple get tool with an output schema. However, it lacks context about its role in the broader connection configuration (e.g., relation to put_connection_ipv6_config or get_connection_config).

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 tool has no parameters, and schema coverage is 100%. The description does not need to add parameter info, and it correctly omits it. The baseline is 3, but the clarity earns a slight bonus.

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 it 'Returns the current ConnectionIpv6Configuration', which accurately describes the tool's action and resource. However, it could be more specific about what the configuration contains, distinguishing it from similar siblings like get_connection_config.

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 over alternatives. Given many get_* siblings, the description should provide context, such as when to query IPv6 config specifically.

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