list_dns_reverse_records

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

The annotations already declare readOnlyHint=true, and the description adds the scope 'in your IONOS CLOUD account', which is useful. However, it does not disclose other behavioral traits like result ordering, pagination, or whether this includes records across all zones. With annotations covering the safety profile, the added scope justifies a 3.

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 sentence that is front-loaded with the core action and resource. Every word earns its place; it is concise without sacrificing clarity.

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 zero-parameter list operation with readOnlyHint provided, this description is nearly complete. It clearly identifies the resource scope (account-level reverse DNS records). The lack of detail about return format is acceptable given the absence of an output schema and the simplicity of the operation.

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?

There are zero parameters and the schema is an empty object, so no parameter documentation is needed. The description adds a small amount of semantic context by stating that all reverse DNS records are returned, which is the baseline 4 for no-parameter tools.

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 a specific verb and resource: 'List all reverse DNS records'. It clearly distinguishes from sibling tools like list_dns_records and get_dns_reverse_record by specifying 'reverse DNS records', so an agent can identify the correct operation without opening schemas.

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 guidance on when to use this tool versus alternatives such as list_dns_records or get_dns_reverse_record. It does not mention any filtering, pagination, or prerequisites, leaving usage context entirely implicit.

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