linkedin_company_profile

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

Discloses credit cost, endpoint sharing, absence of premium/webhook params, and lack of published example response. Acknowledges uncertainty about exact field names, providing honest expectations.

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?

Well-structured with separate sections for credits and notes. Information is relevant, though slightly verbose; could be trimmed without losing clarity.

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?

Given no output schema, description provides reasonable expectations for return fields and acknowledges documentation gaps. Lacks details on error handling or authentication requirements, but adequate for a two-parameter tool.

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% with clear descriptions. Description adds minor context (e.g., id from URL), but does not significantly enhance understanding beyond the schema. Baseline score of 3 applies.

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?

Explicitly states it scrapes LinkedIn company or school profiles by ID. Distinguishes from the sibling person profile scraper by noting the same endpoint but different type parameter. Verb 'scrape' and resource are clear.

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?

Clearly indicates the tool is for company/school profiles and differentiates from the person profile scraper via the type parameter. However, lacks explicit 'when-to-use' versus other siblings like LinkedIn jobs or posts.

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