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

Annotation Contradiction: readOnlyHint is true, but the description explicitly says the tool 'store[s] the results in the user's brain automatically' and tells agents not to re-save them with graph tools. That describes a persistent write side effect, which contradicts the read-only annotation. The rich operational detail is therefore undermined by this inconsistency.

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 front-loaded with the main action, followed by compact, non-redundant sentences about output split, watcher behavior, linking syntax, and the found_by_object_id parameter. Every sentence earns its place despite the paragraph being longer than average.

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?

Without an output schema, the description compensates by explaining the new/seen response split, how to link posts using returned object ids, and the scheduled-watcher reporting rule. That gives an agent everything needed to invoke the tool and handle its return correctly.

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%, so the baseline is 3. The description adds real value for found_by_object_id by explaining that it is the agent's own node id from the [object:...] marker and should be omitted in normal chat; this goes beyond the schema's field description.

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 opening sentence names a specific verb+resource ('Search public LinkedIn posts by keywords') and adds the distinctive side effect (auto-store results), which separates it from sibling read tools like get_my_linkedin_posts or search_connections.

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 description gives clear context: scheduled watcher runs should report only new posts, found_by_object_id should be omitted in normal chat, and results should not be re-saved with graph tools. It does not name an alternative tool to use instead, so it stops short of a full when-to-use-vs-alternative statement.

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