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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered; the description adds genuinely new behavior: results are paginated newest-first and nextCursor must be threaded to read further. It reinforces read-only semantics ('only reads back what is already on their list'). Rate limits and page-size fallback behavior are left to the schema, keeping it just short of a 5.

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?

Front-loaded with the trigger condition, followed by purpose, then the negative boundary, then the url use case, then pagination. Every sentence contributes distinct information with no restatement of the name or the schema, and the 'NOT keyword research' clause is placed where an agent will read it early.

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 detail is rightly omitted, and pagination plus cursor threading are covered. With four optional parameters across list/filter/page concerns, the description is essentially complete; only minor items such as default page size or total-count behavior are left to the schema.

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% and the url parameter is fully documented there, so the baseline would be 3. The description still adds an operational use case for url the schema does not express — checking what a Pin's link already has before calling save_keywords — which meaningfully informs how to use the filter rather than merely restating it.

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?

Opens with a specific verb+resource ('Returns the organization's Saved Keywords list') and immediately bounds the scope. It explicitly distinguishes itself from keyword research AND from write-side siblings like save_keywords, so an agent can select it without opening the schema. Nothing about the intent is left ambiguous.

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 concrete triggering conditions ('when the user asks what keywords they have saved', 'to write Pin titles... pick a board topic... plan content') plus an explicit exclusion ('This is NOT keyword research: it will not discover new keywords or report how a term is trending'). It also names save_keywords as the complementary write path in the context of the url check.

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