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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's only added behavioral signal is the word "verified", which is useful but thin; it does not say whether results can be empty, how many channels come back, or in what shape, and there is no output schema to cover that.

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?

A single front-loaded sentence with no filler — the verb and the returned fields arrive immediately. The only weakness is that it is a bare comma list, so the relationship between "contact channels" and the named fields is left slightly ambiguous.

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 zero-parameter, read-only lookup with full annotation coverage, the description does the one thing that matters: it enumerates what comes back, partially substituting for the missing output schema. It could be stronger by noting what an empty or unverified result looks like, but nothing essential for calling it correctly is absent.

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?

The tool takes zero parameters, so the baseline is 4 with no schema semantics for the description to compensate for. Nothing in the description mischaracterizes the invocation contract.

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?

Uses a specific verb ("Retrieves") plus an enumerated resource set (verified contact channels, email, LinkedIn, timezone, scheduling links), which is far more concrete than the title alone. It is implicitly distinct from the sibling list (portfolio, case studies, articles, tools), but never names or contrasts with any of them.

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?

There is no explicit when-to-use or when-not-to-use statement, no prerequisites, and no named alternative. Usage is only implied by the returned content — an agent infers it should call this when it needs a person's contact details, which is adequate but leaves the routing entirely to inference.

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