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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the bar is lowered. The description still adds meaningful policy detail: emails are only supplied when available and never for EU/EEA/UK companies, results may degrade to a LinkedIn-only title match, and no messages are ever sent.

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 core purpose and return fields are front-loaded, and the compliance caveat is clearly placed. The final sentence ('never writes or sends messages') partly restates the read-only annotation and is slightly redundant, but overall the text is tight and earns most of its space.

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?

There is no output schema, so the description correctly carries the burden of describing what is returned (name, role, LinkedIn, verified email). Combined with annotations covering the safety profile, an agent has enough to call and interpret this tool; only pagination/empty-result behavior is unaddressed.

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?

With a single parameter and 100% schema description coverage, the schema already documents the opportunity_id format and its origin tools (list_opportunities, get_daily_brief). The description adds no syntax or format detail beyond implying 'one lead', so the baseline of 3 applies.

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 resource (the person who most likely owns the project behind a lead) and enumerates the returned fields: name, role, LinkedIn, and email. It is clearly distinct from sibling tools, though it does not explicitly name or contrast any alternative.

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?

Usage is implied via the domain reference to a lead and the note that results are sometimes only a LinkedIn search, but there is no explicit statement of when to call this versus siblings like get_account or list_opportunities. The implicit context is available but no exclusions or prerequisites are stated.

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