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

Annotations already cover readOnlyHint, openWorldHint, idempotentHint and destructiveHint, so the safety profile is known. The description adds genuinely new behavioral context: per-company stablecoin pricing and the rule that a not-found company is not charged. It omits auth/rate-limit details but adds value beyond the 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?

Two sentences, purpose front-loaded, followed by the return-field list and pricing note. No filler, and the output enumeration earns its place since there is no output schema.

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 no output schema, the description compensates by listing the returned fields, and annotations plus the pricing note cover the behavioral contract for this single-parameter read tool. Nothing an agent needs to invoke it correctly is missing.

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% and the single 'companies' parameter is fully documented in the schema (https only, no query string, 1-10 items, per-company pricing). The description restates the 'up to 10 URLs' bound but adds no syntax or format detail beyond the schema, so baseline 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?

States a specific verb and resource ('LinkedIn company enrichment') and enumerates the output fields, so an agent immediately knows it returns company-page records. The resource scope (company pages) implicitly separates it from linkedin-profile-email, linkedin-jobs and linkedin-posts.

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?

Usage is implied by 'send up to 10 LinkedIn company page URLs and get one JSON record per company', but there is no explicit when-to-use guidance or routing to alternative tools (e.g. when to prefer linkedin-profile-email or linkedin-jobs). Adequate but leaves selection to inference.

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