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

Annotations already declare read-only, idempotent, non-destructive, but the description adds substantial context beyond them: 'Spends nothing' (cost), newest-verification-first ordering with 'nothing ranks them', the exact row contents returned, and the non-obvious rule that a private page is absent from lists yet still invitable by exact @handle or ixo1 address.

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?

Opening clause is well front-loaded and dense, but the paragraph is long and runs together listing behavior, ranking, invite flow, private-page rules, and page mode without visual separation. A few clauses (e.g. restating 'who they are, their rate' in both modes) could be trimmed.

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 no output schema, the description fully compensates by enumerating each returned row (identity, LinkedIn verification date, rate, page, invite path) and describing both operating modes. An agent can call and interpret results without further information.

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 already 100%, so the baseline is 3; the description adds real meaning by clarifying that `q` searches the pro's page as the directory search box does, that `handle` accepts an exact @handle or an ixo1 address, and that `available` means open to work now. It largely mirrors the schema, hence not a 5.

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 both modes precisely: listing three to five verified pros filtered by field, and reading one person's public page when `handle` is given. The verb/resource pair is clear, though the two modes are introduced in a slightly shuffled order (page mode appears mid-paragraph) rather than up front.

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 explains when to pass `q` (what the ask needs or free words), when to pass `available` (open to work now), and when to use `handle` (one person's page), and points onward to `invite_to_call`. No explicit when-not-to-use or exclusion against siblings is given, so it stops short of a 5.

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