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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description does add genuinely useful cost behavior (minimum credit charge, repeat requests may re-purchase data), but the pricing passage self-contradicts ('at least 10 Nexscope credits' next to '1 credit per request'), which weakens the value of the disclosure.

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 well front-loaded and informative, but they are followed by unedited supplier boilerplate ('Pinterest User Boards API View Pricing ... Examples are not guaranteed prices') that is repetitive and internally inconsistent. Roughly half the text does not earn its place.

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, listing the returned fields (name, url, description, pin_count, follower_count, owner, cover_images, created_at) is the right compensation. However, it claims cursor pagination while the schema exposes no cursor parameter and gives no page-size or total-count guidance, leaving the pagination contract incomplete.

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 100%, so handle and trim are already explained in the schema and the baseline applies. The description's mention of 'pagination via cursor' adds no usable meaning because there is no cursor parameter in the schema, so the agent gets neither extra parameter detail nor a coherent pagination story.

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 with scope: 'Fetches a paginated list of boards for a Pinterest user', and enumerates the returned fields. It does not name the nearby siblings (social_pinterest_board for a single board, social_pinterest_search, social_pinterest_topic), so the distinction must be inferred from the name alone.

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 use this tool versus the alternative Pinterest tools; the closest is the fragment 'Get a user's boards' pasted from supplier docs. Nothing tells the agent to prefer social_pinterest_board when it already has a board URL, or when a search-based approach is better.

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