list_dns_records

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

The description merely restates the tool name and adds no behavioral context. With no annotations provided, it fails to describe output format, permissions, read-only nature, or any side effects—leaving the agent completely uninformed beyond what the name implies.

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 concise sentence with no wasted words. It is front-loaded and immediately conveys the action, making it easy to process.

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—one optional parameter, no annotations, and an output schema—the description is functionally sufficient. It correctly identifies the operation, and the schema covers parameter semantics, so the agent can invoke it correctly. Slightly more context (e.g., pagination, filtering behavior) would improve completeness, but the core needs are met.

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 input schema provides a full description for the 'filter' parameter ('Filter records by name'), achieving 100% schema coverage. The tool description adds no parameter-specific information, but the schema already handles this, so the baseline score of 3 is appropriate.

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 'List DNS records' uses a specific verb (list) and resource (DNS records), clearly distinguishing it from sibling tools like create_dns_record, delete_dns_record, and list_stacks. The purpose is unambiguous and directly names the core action and object.

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 explicit usage guidance is provided, but the name and description make it obvious this tool is for retrieving DNS records. The sibling tools handle create/update/delete operations, so the use case is implied rather than explicitly stated.

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