Remove records from an RRSet

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

The description adds important behavioral context beyond the destructiveHint annotation by specifying that removing the last record deletes the entire RRSet. This clarifies the scope of destruction, which the annotation alone does not convey.

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?

Two sentences, front-loaded with the action, no redundant information.

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 concise but covers the core behavior and a key edge case. Given the tool's simplicity and the schema's detail, it is mostly complete, though it lacks explicit guidance on when to choose this over delete_rrset or set_records.

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 description explains that records are matched by value, which adds meaning beyond the schema's field descriptions. This clarifies the matching logic for the records array, though the schema already describes individual fields well.

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 removes specific records from an RRSet, using the verb 'Remove' and specifying the resource. It distinguishes from sibling tools like add_records, set_records, and delete_rrset by focusing on removing individual records by value.

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 removing individual records and notes the edge case of last record deleting the RRSet. However, it does not explicitly compare to alternatives like delete_rrset or set_records, leaving the when-to-use guidance implicit.

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