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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real context beyond them: this is a cache of previously discovered identities, freshness is tracked by lastSeenAt, and the call never contacts LinkedIn nor refreshes company permissions — material side-effect information an agent would otherwise have to guess.

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 scope statement is front-loaded in the first sentence and the remaining sentences each carry distinct information (author selection, identity uniqueness, data provenance, freshness, side effects). The opening line merely restates the title, which is the one clearly wasted element.

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?

With an output schema present, return values need not be described, and the description covers scope, identity selection, provenance and side effects adequately. The remaining gaps are pagination behavior with no filters and the stray linkedinActorUrn reference, which is a correctness issue rather than a missing-explanation issue.

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 reported at 0% for the single top-level 'query' parameter, so the description has to carry the load. It explains the intent of linkedinAccountProfileUrl (scope to one connected account) but leaves limit and cursor unexplained and, more problematically, instructs the reader to 'add linkedinActorUrn', a parameter that does not exist in the input schema — an inconsistency that could cause a malformed call.

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 names a specific resource ('identities already discovered for active workspace LinkedIn bindings') and scopes it to a read-only catalog, which clearly separates it from siblings like listComments and listCommentDrafts. It stops short of explicitly naming a sibling it replaces, so it lands at 4 rather than 5.

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 partial selection guidance ('Use linkedinAccountProfileUrl for the personal author; add linkedinActorUrn for a company author') and a useful disambiguation rule that the same company on different accounts counts as a distinct selection. However, it never states when to call this instead of listComments/listCommentDrafts, and it references linkedinActorUrn as if it were an input filter even though it does not appear in the schema.

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