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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, but the description adds genuinely new behavior: the concrete result shape, cursor-based pagination, a trim mode for lighter payloads, and a credit cost. The disclosure that "repeated requests may purchase data again" is exactly the kind of non-obvious side effect annotations cannot express. The cost statements are internally muddled ("at least 10 Nexscope credits" vs. "1 credit per request"), which keeps it from 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?

The first two sentences are front-loaded and earn their place, but the trailing pricing block is raw boilerplate ("Pinterest Search API View Pricing Search Pinterest 1 credit per request") that repeats and conflicts with the earlier cost sentence and adds no decision-relevant clarity.

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 usefully enumerates the returned fields and explains both pagination and the trim tradeoff, which is what an agent needs to call and consume this tool. The only real gap is an unresolved cost figure, which matters for budgeting but not for invocation correctness.

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 67%; trim and cursor are already documented in the schema, and the description only restates them (pagination via cursor, trim for lighter responses). The required 'keyword' parameter has no schema description and the description adds only that it is a query to match pins against, which is minimal but sufficient context.

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 first sentence states a specific verb and resource ("Searches Pinterest for pins matching a query") plus the returned fields, which is far more informative than the tautological title. It does not, however, distinguish this from siblings such as social_pinterest_pin_detail or social_pinterest_topic, so an agent must infer that this is the keyword-discovery surface while those are lookup surfaces.

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?

Usage is only implied by "matching a query" and the pagination/trim notes. There is no explicit statement of when to prefer this over social_pinterest_topic, social_pinterest_board, or social_pinterest_pin_detail, and no prerequisites or exclusions are given.

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