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

With no annotations, the description carries the full burden and does a solid job: it discloses the flat credit cost, that empty/failed results are never charged, and that fresh fetches are the default with an optional free cache hit. This is meaningful behavioral context beyond the input schema, though it does not address error handling or rate limits.

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 description is short and front-loaded with the output shape, but it wastes a sentence on redundancy: 'Flat 1 credit. Costs 1 credit.' say the same thing. The structure is otherwise compact and scannable.

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?

Despite no output schema, the description sketches the return structure (id, socials, titled links, website/email/whatsapp, other[]) and covers cost, failure charging, and caching. It is not fully complete because the cache=true 24h claim clashes with cacheMaxAge's longer TTLs, but for a simple three-parameter fetch tool it provides enough context.

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%, so the baseline is 3. The description adds a concrete 'free 24h cache hit' claim and 'default always fresh' behavior, but this slightly conflicts with the schema's cacheMaxAge options (1d-30d) and the default-TTL wording for cache=true. Thus the added value is marginal and somewhat ambiguous.

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 identifies the resource (lnk.bio pages) and the output shape (id, socials, titled links, website/emailwhatsapp, other[]), making it clear this is a page parser/extractor. It does not use an explicit verb like 'fetch and parse', but the arrow notation conveys the transformation and distinguishes it from sibling tools like linktree_page and komi_page by platform name.

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?

The description gives parameter-level usage guidance ('Pass cache=true for a free 24h cache hit') and cost behavior, but it never states when to choose this tool over siblings like linktree_page, komi_page, linkme_profile, or pillar_page. Usage context is implied by the lnk.bio platform name rather than explicitly articulated.

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