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

With no annotations, the description carries the full burden. It usefully discloses the return shape ('the public profile ... or null') and the input constraint (LinkedIn only), but says nothing about read-only nature, authentication, rate limits, or how unmatched URLs resolve beyond the bare 'null'.

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 tight sentences with no filler, and the essential constraint is front-loaded. The first sentence is a grammatical fragment ('The public profile ... belongs to'), which slightly reduces readability.

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 one-parameter lookup with full schema coverage and no output schema, the description is largely sufficient: it explains the input domain and the returned value, including the null case. Minor gaps around safety/behavior traits remain.

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 url parameter, so the schema already documents the accepted example. The description reinforces the accepted URL forms and rules out email input, adding modest value over the structured field; baseline 3 fits.

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 operation (finding the public profile tied to a LinkedIn person/company URL) and clarifies the input domain. It distinguishes itself from generic search tools by only accepting LinkedIn URL forms, though it does not name specific siblings like search_profiles or get_profile to sharpen the contrast.

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 clause 'LinkedIn only: profiles are never looked up by email' functions as a when-not hint, steering the agent away from email-based lookups. However, it names no alternative tool for those other cases, so the routing guidance is implied rather than explicit.

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