delete_entity_key

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

With no annotations provided, the description carries the full burden. It discloses the disabled state for safety, which is an important behavioral warning. However, it does not mention side effects, permission requirements, or whether deletion is reversible, leaving some ambiguity.

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 one concise sentence with a leading verb and a crucial caveat. No filler or 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?

For a simple two-parameter delete operation, the description plus schema provide enough context. The disabled-state note is essential and addresses the main operational question. It could mention side effects, but for a tool that is disabled, the risk is mitigated.

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 already documents both parameters with clear descriptions (100% coverage), so the description adds no additional parameter semantics. Baseline 3 applies because schema covers parameters completely.

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 the specific verb 'Delete' and identifies the target resource ('alternate key from a Dataverse table'), clearly distinguishing it from sibling tools like add_entity_key and list_entity_keys. It states exactly what operation is performed.

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 phrase 'currently disabled for safety' explicitly signals that the tool should not be invoked, which is critical usage guidance. It does not name alternatives, but the context is sufficiently clear; an agent understands not to rely on this tool.

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