Get Company Profile

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

The description adds no behavioral context beyond the tool's basic function. Annotations already indicate readOnlyHint=true and openWorldHint=true, but the description does not mention that the tool scrapes LinkedIn, may return variable data, or what happens with invalid company names.

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 sentence with no filler. It is appropriately sized for the tool's simple purpose.

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?

The tool has a well-documented schema and an output schema, and annotations provide safety hints. However, the description omits how the optional 'sections' parameter relates to the sibling get_company_posts tool, and it doesn't state that the about page is always included, which is only in the schema. This creates some ambiguity for tool selection, but overall the structured data covers most essential information.

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 has detailed descriptions for both company_name and sections, achieving 100% coverage. The description itself does not add any parameter semantics beyond the schema, so it meets the baseline for high schema coverage.

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 'Get a specific company's LinkedIn profile' uses a clear verb (get) and resource (company's LinkedIn profile). It is distinct from siblings like get_company_posts or search_companies, which target different resources.

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 gives no guidance on when to use this tool versus alternatives such as get_company_posts or search_companies. It does not mention the sections parameter or any exclusions, leaving the agent to infer usage from the schema.

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