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

Annotations already supply read-only/idempotent/non-destructive hints; the description adds value by disclosing that results are named by field and that the lead contains personal data that may be shown but never republished. It repeats read-only/'free' status without contradicting any annotation.

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?

Three short sentences pack identity, return-shape, and handling policy with no filler. The key scoping phrase ('One LinkedIn lead by id') is front-loaded.

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 one-required-parameter read tool with strong annotations, the description is nearly complete: it explains where the ID comes from, what output to expect, and the sensitive-data policy. It doesn't specify error/not-found behavior, but that is a minor gap for a simple read by ID.

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 schema already describes pageId and adAccountId in useful terms; the description mainly clarifies leadId's provenance ('by id (from list_linkedin_leads)'). With 67% schema coverage, this is adequate but not a major contribution beyond the schema.

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 specific operation — retrieving one LinkedIn lead by ID — and ties the ID to list_linkedin_leads, which distinguishes it from the list/collection siblings. It also communicates the output characteristic ('every answer named by field').

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?

It clearly locates the tool in a workflow: after listing leads, pass a lead ID to read that single lead in full. It doesn't name sibling alternatives or state when not to use it, but the contextual signal is strong and the privacy instruction gives a use restriction.

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