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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description's added value is in disclosing that results are filtered: Google-derived or unverified text is withheld before matching and full shared post text is absent. That is genuine behavioral context an agent cannot infer from annotations. It does not, however, say what happens when a cursor is exhausted or how many results a page yields.

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 compact sentences with the core action and pagination front-loaded, and no filler. The third sentence slightly restates the second's withholding point, but overall it is tight.

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?

An output schema exists, so return shape need not be explained, and the filtering caveat is well covered. The gap is on the input side: with three undocumented parameters and the meaning of "query" matching unstated, an agent cannot predict what a search will surface or how to page reliably.

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 description coverage is 0% across all three parameters, so the description carries the full burden and largely fails it. It hints that paging is bounded but never explains what limit bounds, what cursor represents, or which fields query matches against, and it omits the schema's max of 20 entirely.

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?

"Searches saved posts with bounded pagination" gives a specific verb (searches) plus resource (saved posts) and a scope qualifier, which lets an agent distinguish it from list_ideas, list_threads, and search_sources. It stops short of explicitly naming which sibling to use for other content types.

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?

There is no statement of when to reach for this tool over siblings such as search_sources or list_threads, nor any prerequisites or exclusions. The only usage-adjacent hint is "bounded pagination," which is a mechanic rather than routing guidance.

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