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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description does add genuinely useful cost behavior (credits are charged per completed lookup and repeated requests may purchase the data again), but the pricing text then contradicts itself between "at least 10 Nexscope credits" and "1 credit per request," which muddies rather than clarifies the cost model.

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 front-loaded field enumeration is useful and well placed, but the trailing block ("LinkedIn Company Page API View Pricing Get a LinkedIn company page 1 credit per request...") is pasted marketing boilerplate that repeats and contradicts the earlier credit statement. Those sentences do not earn their 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 one parameter, annotations covering the safety profile, and no output schema, the main thing an agent needs is what the response contains — and the description lists the returned fields in detail. Only the ambiguous pricing wording and missing alternative-tool guidance keep it from being fully complete.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that 'url' is the LinkedIn company page URL. The description adds nothing beyond that — no note on accepted URL forms (slug vs. full URL, trailing path segments) — which is the baseline for this coverage level.

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 opens with a specific verb and resource ("Fetches a LinkedIn company page") and enumerates the returned fields, so an agent knows exactly what comes back. It is not fully differentiated from siblings such as social_linkedin_company_posts or social_linkedin_profile, and mentioning "recent posts" as a returned field slightly blurs the line with the posts tool.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The agent must infer that this tool is for a single company page's full profile rather than its posts, employees, or ad activity, which is a real routing risk in a catalog this large.

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