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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: that bookmarks retain only search parameters and never results, which prevents an agent from expecting cached data back.

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 clauses, front-loaded with the read-only marker and the resource, then the enum values, then the follow-up action. The inline value list is long but necessary and no sentence is wasted.

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 single-parameter read-only list tool with no output schema, the description covers what it returns conceptually, the meaning and allowed values of the only parameter, and what the caller should do next. Only the exact returned record structure is left implicit, which is minor.

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 0% and `kind` has no enum, so the description carries the full burden — and it does, enumerating all nine accepted values (news, gservice-trends, gservice-maps, twitter-trends, tt-trends, yt-trends, ig-trends, rd-trends-search, rd-trends-subreddit) and defining `kind` as the page the search came from.

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: returning the caller's saved trend search bookmarks for one list, with `kind` identifying the source page. It is clearly distinct from create_trends_bookmark and delete_trends_bookmark, 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?

Gives a clear usage context and a concrete next step — a bookmark stores only `trends_bookmark_params`, never results, so it must be re-run with the matching list/search tool. It stops short of explicitly saying when to prefer this over sibling bookmark tools, but the operational guidance is solid.

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