linkfetch_get_profile

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

With no annotations, the description must carry the behavioral burden, and it discloses a genuinely important failure mode: cache-first with an `extension_required` error on miss instructing use of the Chrome extension. It omits auth prerequisites and any rate-limit behavior, which is notable given sibling safety tools exist.

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 sentences, zero filler. The capability and input contract come first, the cache/error caveat second — correctly front-loaded.

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?

Enumerates the return payload in lieu of an output schema and covers the error path, so an agent can act correctly. Missing only prerequisite/permission context and rate-limit awareness, which matter for a scraper-style tool in this toolset.

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 100%, so 3 is the baseline, but the description adds real value the schema cannot express: the mutual-exclusivity constraint 'exactly one of url or slug', which is not encoded as a oneOf in the schema.

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?

Specific verb+resource ('Fetch a full LinkedIn profile') with an explicit enumeration of the returned fields and the two accepted identifiers. It is trivially distinguishable from siblings like linkfetch_search_people or linkfetch_get_company.

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?

Gives clear invocation context ('Provide exactly one of `url` or `slug`') and states the cache-first path. It does not, however, tell the agent when to prefer this over linkfetch_search_people (search vs. direct fetch) or what happens on a cache hit.

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