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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds only the conceptual meaning of a 'rule' (a new-lead notification) but says nothing about result volume, ordering, ownership scope, or whether it returns disabled rules.

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?

One short, front-loaded sentence with no filler; the key noun phrase leads. It is lean, though it is lean partly by omission rather than by tight editing.

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 read-only list tool with two undocumented required parameters, no output schema, and no return-shape or pagination notes, the description leaves real gaps. The annotations carry the safety story, but scope, filtering, and result format are entirely absent.

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% for two required string parameters (projectId, siteId), and the description supplies no parameter meaning at all — it never explains that the rules are scoped to a project/site. With the schema silent and 0% coverage, the description should have compensated but does not.

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?

Clear verb+resource ('List the rules') with a scoping gloss ('that notify the user about new leads') that distinguishes this from list_lead_keywords or list_lead_icp. However, it does not acknowledge the sibling operations create_lead_alert_rule, delete_lead_alert_rule, or set_lead_alert_rule_status, so an agent must infer the read-only listing role from the name alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. Nothing tells the agent when to call this versus the create/delete/status siblings or versus other lead-listing tools.

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