Delete discovery lead

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

With no annotations, the description carries the full burden. It explicitly states the destructive nature ('Permanently remove'), side effects ('shifting rows below it up'), safety measures ('backs up first'), refusal conditions ('missing/ambiguous matches'), and return value ('returns the deleted row'). This is thorough behavioral disclosure.

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, front-loaded with the action and resource, and every clause adds value. There is no redundancy or padding.

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 2-parameter delete tool with no annotations and no output schema, the description is highly complete. It explains the matching key, side effects, safety behavior, failure conditions, and return value, which is sufficient for an AI agent to use it correctly.

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 both parameters are described, but the description adds meaning by establishing that company and position are used together as a composite match key. It also adds behavior for ambiguous/missing matches, going beyond the schema's simple field descriptions.

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 ('Permanently remove') with a clear resource ('discovery lead') and matching criteria ('company + position'). It clearly distinguishes from sibling tools like discovery_add, discovery_update, and delete_job.

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 clearly indicates when to use this tool—to permanently delete a discovery lead—and provides context about its behavior (e.g., refuses missing/ambiguous matches, backs up first). It does not explicitly mention alternatives, but the scope is unambiguous.

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