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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the page must be public and each call 'Costs 1 credit', which materially affects invocation decisions. It stops short of covering failure modes for private/missing pages.

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?

Two compact sentences with the payoff (what you get back) front-loaded alongside the credit cost. The leading 'Lnk.Bio page.' fragment is mildly redundant with the title but does not waste much 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?

With no output schema, the description carries the burden of describing the return value and does so explicitly (display name, bio, avatar, ordered links), plus cost and the public-only constraint. For a 2-parameter read tool this is sufficient to call correctly.

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 url parameter is well documented in the schema (full URL or username), but the description adds nothing about input format. cache_max_age is undocumented in both schema and description, so half the parameters remain opaque; the description does not compensate for that 50% coverage gap.

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 names the specific resource (a public Lnk.Bio creator page) and enumerates the returned content: display name, bio, avatar, and ordered outbound links. It is clear what the tool fetches, but it never distinguishes itself from the many sibling link-in-bio retrievers (linktree_page, linkme_page, komi_page, taplink_page, solo_page, pillar_page).

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 guidance on when to pick this over linktree_page or the other link-in-bio siblings, and no prerequisites or exclusions are stated. The only implicit cue is 'Public Lnk.Bio page', leaving 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.