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

The annotations already establish that this is a safe, read-only, idempotent operation. Beyond that, the description adds meaningful behavior: rules are per LinkedIn account, affect every campaign on that account, and filter prospects before they enter campaigns.

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 front-loaded with the resource definition and then adds only the scope, diagnostic use, and alternative. There is no wasted text, and the per-account versus per-campaign distinction is stated efficiently.

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 read-only list with fully described parameters and clear annotations, the description is nearly complete. The main gap is that it does not state what happens when `linkedAccountId` is omitted, even though the schema marks it optional.

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%, so the three parameters are already documented by the schema. The description reinforces the account-level scope but does not add format or behavior details beyond what `linkedAccountId`, `page`, and `pageSize` already provide.

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 defines the resource as exclusion rules for a LinkedIn account and explains their effect: matching prospects are filtered before entering campaigns. It distinguishes this list from the per-campaign exclusion alternative, though the retrieval verb itself is only implied by 'Read it' rather than stated directly.

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 gives an explicit diagnostic use case: read this when a search returns fewer leads than expected. It also names the alternative for a different need, `lead_update` with `isExcluded`, and clarifies the per-account scope that separates this tool from per-campaign exclusion.

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