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

With readOnlyHint and openWorldHint already declared, the description adds genuine context beyond annotations: it discloses the exact payload (profile fields plus ordered outbound links) and, importantly, the cost ('Costs 1 credit'), which is the kind of rate-limit/cost signal agents need. It stops short of covering caching behavior or failure modes, so not a 5.

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 tight sentences with the payload description front-loaded and the credit cost clearly flagged. The opening fragment 'LinkMe page.' duplicates the title and is slightly wasteful, but overall the text is efficient.

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?

No output schema exists, so the description carries the burden of explaining return values, and it does so concretely. Cost is disclosed. The only material gap is the undocumented cache_max_age parameter, which is minor for a read-only fetch.

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 only 50%: 'url' is documented in the schema with a format example, but 'cache_max_age' is undocumented everywhere. The description contributes nothing about either parameter, so it fails to compensate for the 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 LinkMe creator profile) and enumerates its contents: display name, bio, avatar, and outbound links in order. That is far more than a restatement of the name. It does not, however, distinguish this from near-identical siblings such as linktree_page or linkbio_page, so it falls short of a 5.

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 rather than stated: an agent can infer this fetches a link.me profile, and the schema's URL example reinforces that. But there is no explicit when-to-use, no exclusion, and no pointer to linktree_page/linkbio_page for other providers.

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