Clear Stored Leads

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

No annotations are provided, so the description bears the full burden of disclosing behavior. It clearly states a destructive action ('Delete all'), which conveys that it is a mutating operation. However, it does not explicitly mention irreversibility, the requirement for confirmation, or any side effects beyond the deletion itself. The description essentially restates the tool name and title without adding further context.

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 that is well-structured and front-loaded. It contains no filler or redundant information, earning its place as an efficient summary of the tool's purpose.

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 one-parameter destructive tool, the description is mostly sufficient. It accurately conveys the primary action and scope. However, it lacks any mention of when to use the tool or the confirmation safety mechanism, which would be helpful given the absence of annotations and the existence of sibling tools that might be confused with it.

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 has one required parameter 'confirm' with a const value of true, which is self-explanatory. The description does not mention the parameter at all, and schema description coverage is 0%. However, the schema's 'const' and 'required' fields sufficiently convey that confirmation must be true, so the schema compensates for the lack of description-level parameter guidance.

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 'Delete all locally stored lead records' uses a specific verb ('Delete') with a clear resource and scope ('all locally stored lead records'). It distinguishes itself from siblings like list_stored_leads (read-only) and export_leads (reads/exports) by clearly indicating a destructive operation.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as exporting or listing leads first. Sibling tools like list_stored_leads and export_leads exist, but the description does not address when deleting is appropriate or what safety checks to perform.

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