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

Annotations indicate destructiveHint=true, and the description adds important context: the confirm parameter requirement, prerequisite permission checks, and free business restriction. No contradiction with annotations.

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 four sentences, front-loading the action and covering key points. While each sentence adds value, the length is slightly above optimal but acceptable for the complexity.

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 no output schema and destructive annotations, the description adequately covers the action, preconditions, and warnings. It lacks details on return value or post-deletion effects, but that is typical for delete operations.

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 has 3 parameters with 0% description coverage. The description adds meaning for the confirm parameter ('requires confirm set to DELETE'), but does not explain formId or communityId, which are left to the schema's minimal type and minLength constraints. Partial compensation.

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 lead form,' using a specific verb and resource. It effectively distinguishes itself from sibling tools like duplicate_lead_form or get_lead_form by focusing on deletion.

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 explicit when-to-use and when-not-to-use guidance: requires confirm set to DELETE, check business permissions, FREE businesses cannot use, call check_business_tool_access before collecting inputs, and never proceed when access is blocked.

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