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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavior: result ordering, the pagination scheme, and how unsynced_for resolves against a CRM sync marker. It omits the default/maximum page size and return row shape, which are the remaining useful disclosures.

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 dense sentences with the core scope and ordering front-loaded, and every filter clause earns its place. It does restate the status enum that already exists in the schema, which is mild duplication rather than waste.

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 still conveys ordering, row granularity (conversations, not messages), and pagination cursor semantics, which is enough to call it correctly. The absence of any hint about returned conversation fields or total counts is a minor residual gap.

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 only 57%, and the description compensates well: it defines before as the last_message_at of the last row, explains unsynced_for as 'after its mark_synced marker, or never synced', and lists all status enum members. Only limit and company are left to the schema alone.

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 conversations Quibbly has synced') plus default ordering ('newest activity first'), which immediately separates it from read_conversation and search_messages. An agent can tell what this returns without opening the schema.

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?

Explicitly routes message retrieval to read_conversation and enumerates the filter axes, giving clear context for when to call it. It stops short of stating exclusions (e.g. use search_messages for text search, or list_follow_ups for follow-up tracking), so routing is clear but not exhaustive.

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