delete_data_record

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Delete' (destructive) but does not explain side effects, authorization requirements, rate limits, or implications of the 'conditional save plan'. This is insufficient for a destructive operation.

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 two sentences, concise and front-loaded with the primary action. However, it could be slightly more structured to separate purpose from requirements. Overall, no waste.

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 lack of annotations and output schema, the description does not provide enough context about behavior (e.g., what happens on success/failure, handling of conditional save plan, or interaction with credentials). A delete operation with nested parameters needs more completeness.

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?

Schema coverage is 100%, and the schema already provides detailed descriptions for all parameters, including examples for dataViewParameters. The description adds 'Requires primary key(s)' which aligns with schema but does not add significant new meaning beyond structured data.

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 'Delete a data record' and specifies it is for savable Data Pages and data object classes, distinguishing it from other deletion tools like delete_case or delete_attachment. However, it could more explicitly differentiate from sibling tools like update_data_record_full.

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 mentions prerequisites (conditional save plan, primary keys) but does not provide guidance on when to use this tool versus alternatives (e.g., when to delete vs. update) or when not to use it. The context is implied but not explicit.

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