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

Beyond the readOnly/openWorld annotations it adds genuinely useful context: billing impact, cached-vs-live behavior, the fact that contact fields come from the submitted public page, and a data-removal path. However it undercuts itself by stating 'Completed lookups cost at least 10 Nexscope credits' and then '1 credit per request' in the same paragraph, leaving the agent unsure of actual cost. That internal inconsistency weakens otherwise strong disclosure.

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 sentence is well front-loaded, but it is followed by pasted docs navigation residue ('Linktree Linktree page API View Pricing Linktree page 1 credit per request'), a duplicated title in the tool title and description, and a caching paragraph copied verbatim from the schema. Roughly half the text does not earn its place.

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 does the right thing by enumerating returned fields (id, username, profilePictureUrl, description, verticals, timezone, links with id/type/title/url, detected socials, email_address). But the contradictory credit figures and the absence of any note on failure modes (private/nonexistent Linktree URL) leave it short of complete for a paid live-scrape tool.

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 with an enum, so the schema does the heavy lifting and baseline is 3. The description restates the cache_max_age explanation nearly verbatim from the schema rather than adding new meaning such as what a stale-but-cached response means for downstream freshness.

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?

States a specific verb and resource: 'Scrapes a Linktree page by URL, extracting the creator's profile and all their links.' This clearly distinguishes it from generic web scrapers in the sibling list, but it never names its nearest analogues (social_linkbio, social_linkme), so the differentiation is left to the agent's inference from the platform name alone.

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 only real usage guidance is cost/caching: how cache_max_age trades 0 credits for 1 credit. There is no statement of when to prefer this over social_linkbio or social_linkme for a creator's link-in-bio page, and no prerequisites or exclusions. Usage is implied by the platform name rather than explained.

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