Linktree page

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

Annotations declare openWorldHint=true, destructiveHint=false, idempotentHint=false, readOnlyHint=false, and the description goes further by disclosing credit consumption, the confirm=true gate, and that these read-like POSTs do not publish to social platforms. The removal-request/email path and the source of contact fields add genuine context. This is a solid, non-contradictory disclosure that enriches rather than restates 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?

Front-loaded with the core purpose, then the return shape, then behavioral caveats. The return-field enumeration is verbose, but since no output schema exists it earns its place. No filler or redundancy across the operational sentences.

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 compensates by enumerating the returned fields (profile, links array, social accounts, email). Combined with the credit/confirm/annotation coverage, an agent has enough to invoke it correctly; only the absence of an explicit alternative-selection note keeps it from a 5.

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 url, account, confirm, and cache_max_age are already documented in the schema; baseline is 3. The description reinforces the confirm/credit constraint but adds no syntax or format detail beyond the schema for any parameter.

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 (scrapes) and resource (a Linktree page by URL) and enumerates the extracted content (profile, links, social accounts, email). It clearly delimits what this tool covers, though it never names the near-siblings (linkbio_linkbio_page, komi_komi_page, pillar_pillar_page) that an agent might confuse it with.

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 implies usage (you supply a Linktree URL) and adds the operational preconditions 'requires confirm=true' and 'potentially consumes paid API credits', which is meaningful guidance. However, it gives no explicit when-to-use/when-not framing relative to the other page-scraper siblings, leaving routing to inference.

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