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

With no annotations at all, the description carries the full burden; it discloses that results are scoped to the authenticated user and that the payload is profile IDs, which are meaningful behavioral facts. It omits volume/pagination behaviour, ordering, and what happens when the user has no tracked profiles.

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 short sentences with no filler, and the identity/scope statement is front-loaded before the return-value note. Every sentence carries information.

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?

There is no output schema, so the description must describe returns, and it does at a high level ('profile IDs'). For a no-param list tool, however, an agent still cannot tell how many profiles come back, whether anything besides IDs is included, or how to page through results.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is an empty object and the description correctly implies no input is required.

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 ('List all tracked LinkedIn profiles') plus the scope ('for the authenticated user'), which separates it from catalog-search siblings like linkedin_people_search. It never names a sibling directly, so an agent must infer the boundary between 'tracked profiles' and searched profiles.

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?

'Returns profile IDs needed by other tools' implies a discovery-then-fetch workflow, which is useful context. But there is no explicit statement of when to call this versus linkedin_people_search, linkedin_profile_info, or get_profile_summary, and no prerequisites or exclusions.

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