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

Annotations already cover readOnly and openWorld, and the description adds genuinely new context: the page is public data, the returned shape is a creator profile, and the call costs 1 credit. It does not disclose failure behavior for invalid/nonexistent usernames or how the cache interacts with freshness, which keeps it from 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 short sentences, front-loaded with the return contents, and the credit cost is stated plainly. The opening 'Linktree page.' merely restates the tool title and earns little, but nothing else is wasted.

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 return-value burden and does so precisely by listing the profile fields and link ordering. For a two-parameter read-only lookup, the only real gap is the undocumented cache parameter, which is minor.

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 well documented in the schema, but cache_max_age has no description anywhere. The description never mentions either parameter, so it does not compensate for the undocumented caching parameter or clarify its units and defaults.

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 resource and enumerates exactly what is returned: display name, bio, avatar, and every outbound link in order. The platform name (Linktree) distinguishes it from platform-specific siblings like linkbio_page, linkme_page, and taplink_page, but the description never explicitly says how it differs from those link-in-bio tools.

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 only implied: the agent infers it should call this when it has a Linktree URL or username and wants the profile plus links. There is no explicit when-to-use, no when-not-to-use, and no routing to the many sibling link-in-bio tools, so an agent facing an ambiguous URL must guess.

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