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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description contributes the merchant-scoping detail, which tells the agent it cannot target other merchants' records, but it does not say whether deletion is hard or soft, whether related submit events cascade, or what happens if the record is absent (relevant despite the idempotent hint).

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?

A single front-loaded sentence with zero filler: verb, resource, identifier variants, and scope all in one pass. It is arguably too terse given the gaps elsewhere, but nothing in it is wasted.

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 destructive, non-read-only tool with no output schema and 0% parameter documentation, the description does not cover required-identifier rules, failure behavior, or the effect of deletion. The annotations carry the safety flag, but the agent still lacks enough to know it must supply one identifier and what a successful call changes.

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 description coverage is 0%, so the description must compensate, and it does name both parameters and signal that either identifier is acceptable. However, it never states that exactly one is required (both are nullable with default null and zero required params), nor how conflicts between id and uuid are resolved, leaving a real ambiguity in a 2-param destructive tool.

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?

Specific verb (delete) plus specific resource (a single lead submission), and the parenthetical naming `leads_submit_id`/`leads_submit_uuid` makes clear it targets one record by identifier. It implicitly distinguishes itself from the sibling delete_lead (deletes the lead, not the submission), but never says so explicitly, so sibling differentiation is left to inference.

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?

No guidance on when to delete a submission versus related siblings (delete_lead, set_lead_submit_stage, list_lead_submits), no prerequisites, and no warning about irreversibility or how to recover. The only contextual statement is 'scoped to the caller's merchant', which is a constraint, not usage guidance.

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