get_company_profile

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply says 'Fetch full LinkedIn company page data' but does not explain any behavioral traits such as authentication requirements, rate limits, error handling, or the structure of the returned data. The adjective 'full' hints at completeness but adds little actionable detail.

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 a single clear sentence with no extraneous words. It is front-loaded with the action and resource, making it easy to parse quickly. This is appropriately concise for the tool's simplicity.

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 that there is no output schema and no annotations, the description is insufficient for an agent to fully understand the tool's behavior. It does not mention what 'full company page data' includes, the format of the response, potential errors, or any preconditions (e.g., URL format validation). The tool is simple, but the lack of contextual detail reduces its completeness.

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 schema has 0% description coverage, so the description must compensate. It mentions 'for a given URL,' which clarifies that the linkedin_url parameter should be a LinkedIn company page URL. However, it does not provide format expectations or examples, and the parameter name itself already conveys most of the meaning.

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 states the tool's function: 'Fetch full LinkedIn company page data for a given URL.' It uses a specific verb ('fetch') and resource ('LinkedIn company page data'), and it distinguishes itself from siblings like get_personal_profile and get_facebook_profile by focusing on company pages and LinkedIn specifically.

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 implies usage for LinkedIn company URLs but does not explicitly state when to use it over alternatives like get_personal_profile or scrape_website. There is no mention of exclusions or alternative tools, leaving the agent to infer the appropriate context from the resource type mentioned.

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