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

With annotations present, the description usefully adds a hard rate limit (one request per 3 minutes), a runtime precondition (LinkedIn tab must be open), and a note that LinkedIn's own limits still apply downstream. It does not explain why destructiveHint=true for a sync trigger or what state is created/overwritten, which is the remaining behavioral gap.

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?

Three short sentences, front-loaded with the action, followed by the precondition and limits. No sentence is redundant or padded.

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 zero-param, no-output-schema tool the description covers preconditions and rate limits well. What it omits is whether the call returns immediately or blocks, and that the agent should follow up with sync_status to observe progress — a relevant gap given a sibling of that name exists.

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 the schema carries no semantic burden and the baseline of 4 applies. The description implicitly confirms this is a fire-and-forget trigger with no arguments.

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 and resource: trigger an inbox sync now via the extension. It is immediately distinguishable from the read-only sync_status and mark_synced siblings, though it never names those siblings explicitly.

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 precondition 'if a LinkedIn tab is open' is a genuine usage constraint that tells the agent when the call can succeed. However, there is no explicit routing guidance such as when to use this versus polling sync_status, or when a manual sync is preferable to waiting for a scheduled one.

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