Find Linkedin Company Profile from Name

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

Annotations declare readOnlyHint and openWorldHint. Description adds credit cost, a warning about the hidden 'confidence' field, and that it outputs linkedinCompanyURL. Does not cover error cases or rate limits, but adds meaningful context beyond annotations.

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?

Description is front-loaded with purpose, includes credit cost, workflow notes, and parameter list. However, it redundantly repeats the purpose phrase. Still concise enough with most sentences earning 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?

For a simple single-parameter tool with no output schema, the description provides sufficient context: input, output (implicitly LinkedIn URL), workflow position, credit cost, and a hidden field warning. Covers the essential aspects.

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% for the single parameter queryValue. Description simply restates 'Company name column', adding no new semantic meaning or usage examples beyond 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?

The description clearly states it finds a LinkedIn company profile from a name, specifically returning the LinkedIn URL. It differentiates from siblings by positioning itself as the entry point for company workflows, before enrich_companies.

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?

Explicitly states it is the entry point and should be used before enrich_companies. Also mentions it produces the linkedinCompanyURL needed by find_email, providing chaining guidance. Credit cost is noted.

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