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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered; the description still adds real context beyond that: where contact fields originate (public page), a removal/opt-out path via support email, and the cache-vs-live-scrape behavior. The cost statements conflict with each other ('at least 10 Nexscope credits' vs '1 credit per request'), which undercuts an otherwise useful disclosure without contradicting the annotations.

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 opening sentences are front-loaded and useful, but the tail contains pasted marketing noise ('Linkbio Linkbio page API View Pricing Linkbio (lnk.bio) page 1 credit per request') and a verbatim duplicate of the cache_max_age schema text. The two credit figures contradict each other, forcing the agent to reconcile boilerplate.

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 correctly carries the return-value burden by enumerating profile fields and the shape of each link object (url + text). Cost and caching are covered, though the contradictory credit amounts leave the agent unsure about pricing and there is no note on rate limits or failure modes.

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 100% and both parameters are documented there, including the cache_max_age enum values. The description restates the caching semantics (0 credits cached vs 1 credit live) rather than adding new meaning, so the baseline 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 first sentence gives a specific verb (scrapes) plus resource (Linkbio / lnk.bio page) scoped by URL, and the second sentence enumerates exactly what is returned (handle, id, social accounts, email, website, links array). Naming the domain lnk.bio implicitly separates it from the sibling social_linktree and social_linkme scrapers.

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 only implied: the tool takes a lnk.bio page URL and the caching paragraph hints at a reuse-vs-live-scrape tradeoff. There is no explicit statement of when to prefer this over social_linktree/social_linkme or social_find_social_profiles, and no when-not-to-use guidance.

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