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

No annotations are present, so the description carries the full burden. It usefully discloses the flat credit cost, that empty results and failures are not charged, and the cache behavior. However, the pricing wording is redundant and slightly ambiguous: 'Flat 1 credit. Costs 1 credit.' followed by 'free 24h cache hit' leaves uncertainty about whether cache hits consume a credit.

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 compact and front-loaded with the tool's purpose. It loses points because 'Flat 1 credit. Costs 1 credit.' directly repeats the same fact, wasting one sentence. The rest is dense 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?

For a simple single-URL fetch tool with fully documented parameters, the description covers the main outputs, cost, and caching. Still, without an output schema, a bit more specificity about the socials{} structure and row format would help, and the Komi-only URL constraint is left to the schema rather than the description.

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?

The input schema already documents all three parameters with 100% coverage, so the baseline is 3. The description adds only a hint about cache=true and default freshness, but does not explain url format or cacheMaxAge beyond what the schema already states.

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 clearly identifies the resource (Komi link-in-bio page) and what data it returns: identity, socials, and content LINK/PRODUCT rows with price/currency. This distinguishes it from similar link-in-bio siblings like linktree_page and linkme_profile. It lacks an explicit verb such as 'fetch' or 'extract', relying on the arrow notation, so it stops just 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?

The description does not say when to prefer this tool over the many sibling tools for other link-in-bio platforms, nor does it mention any exclusions or alternatives. The 'Komi' label implies the intended platform, but there is no explicit routing guidance for the agent.

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