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

No annotations exist, so the description carries the full burden and does so well: it discloses credit pricing per detail level (11 / 7 / 33), that caching is bypassed via `fresh`, that a failed call is refunded, and that `with_email` performs mail-server verification of each address. This is exactly the operational context an agent cannot get from the schema.

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 sentences, front-loaded with the payload fields, then the email caveat, then the invocation rule and cost. Every clause earns its place and nothing is repeated from the schema verbatim.

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 4-parameter, no-output-schema tool this is complete: fields returned, the extra email behavior, mutual-exclusion of the locators, cache behavior, and full cost model are all present. An agent can call this correctly without further inference.

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 baseline is 3, but the description adds genuine meaning: it explains what `detail=with_email` does beyond the enum label (whole profile plus a work-email search delivered in `emails`) and imposes the mutually-exclusive url/vanity_name rule. It does not restate the enum semantics for `full` versus `main` in as much depth as the schema does.

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?

States a specific verb (Fetch) and resource (LinkedIn profile), enumerates the returned fields (full_name, headline, experience, education, skills, etc.), and scopes it against the sibling family of get_linkedin_* tools by making clear this is the person-level profile fetch.

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?

"Use this to enrich a person from their profile URL" plus "Give exactly one of `url` or `vanity_name`" gives clear context and an invocation constraint the schema itself does not enforce (both are optional). It stops short of naming a specific alternative such as search_linkedin_people for discovery versus enrichment.

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