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

Despite annotations including readOnlyHint=false, the description clarifies it's a provider read that persists continuation state and enforces rate limits across UI and MCP. It also warns to respect RELATIONS_SYNC_PROTECTED retry_after_seconds, adding behavior not visible in annotations. There is no contradiction with the annotations; the idempotentHint is consistent with atomic enforcement.

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 compact but dense, front-loading the core purpose and scope in the first sentence, then adding important behavioral constraints. Every sentence adds value; no filler.

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 tool with no output schema, the description covers what the tool does, its limitations, its statefulness, and rate-limit behavior. The only potential omission is what the response looks like, but the mention of continuation cursor and sync ID implicitly covers that. Given the complexity, this is complete.

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 schema already describes all three parameters (limit, cursor, sync_id) with 100% coverage. The description adds value by explaining the continuation state relationship ('persists continuation state') and the caps, but doesn't add much beyond schema for individual params. Baseline 3 is elevated because the context of continuation and rate-limiting clarifies how parameters interact.

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 states a specific verb ('Synchronize'), a precise resource ('one provider-safe page of the API-key owner's 1st-degree LinkedIn relations'), and explicitly distinguishes itself from a LinkedIn people search. It clearly conveys the action and scope.

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?

It explicitly says this is a provider read, not a people search, and does not consume search quota—this directs the agent to use this instead of search_linkedin_people when syncing relations. The description also includes rate-limit guidance (hourly/daily caps, retry_after_seconds) and mentions continuation state, giving clear context for when and how to invoke it.

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