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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description must clarify the mutation. It adds that the list is created empty, which is a key behavioral detail. The openWorldHint=true is not contradicted; the description is consistent and provides enough context that the tool creates a list with no leads.

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?

Two concise sentences with no redundant wording. The purpose is front-loaded, and the sibling reference is brief and useful. Every word earns its place.

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 creation tool, the description is sufficient: it states the purpose, mentions the empty nature, and points to the next step. It does not describe return values, but no output schema exists, so that is not required. It lacks details on name conflicts or permissions, but those are minor for this simple operation.

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% with both parameters (name and description) well documented. The tool description does not add any additional semantics about the parameters beyond what the schema already provides, so the baseline of 3 applies.

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 states a clear verb ('Create') and a specific resource ('empty lead list'), and the qualifier 'empty' distinguishes it from sibling tools like add_leads_to_list and delete_list. An agent can immediately understand that this tool creates a list without adding leads.

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 explicitly instructs to use add_leads_to_list to fill the list, providing a direct alternative and when to use it. This is clear guidance that routes the agent to the correct sibling for the follow-up operation.

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