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

Annotations already declare readOnly, openWorld, and non-destructive, so safety is covered; the description goes further by disclosing pagination behavior, exactly what trim retains versus drops (only the nested leaves, not full objects), that save counts and visual annotations are not guaranteed, and the credit cost model with a warning that repeated requests may purchase data again. The only weakness is that the cost text is internally inconsistent (10 credits minimum stated early, '1 credit per request' appended later), which could confuse an agent.

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 core is front-loaded, but the text is bloated with injected pricing boilerplate and repeats the trim behavior and save-count caveat multiple times ('With trim=true ... native save counts and keyword labels' appears in two places), plus 'Get pins from a Pinterest board' duplicates the opening sentence. Several sentences do not earn their 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?

There is no output schema, and the description compensates by enumerating the returned pin fields and detailing what trim preserves, plus stating the cost model and pagination mechanism. An agent has enough to call it correctly, with only the contradictory credit figures as a minor gap.

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 all three parameters are already documented in the schema. The description largely restates the trim behavior and cursor pagination rather than adding syntax or format details beyond the schema, so the baseline of 3 applies despite the extra emphasis on trim semantics.

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 opening sentence gives a specific verb and resource: fetches a paginated list of pins from a Pinterest board by URL, and it enumerates the returned fields (pin id, description, title, images, board info, pin_join, aggregated_pin_data). However, it never distinguishes this from siblings like social_pinterest_user_boards, social_pinterest_pin_detail, or social_pinterest_topic, so the agent gets no help choosing between them.

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: the description explains that pagination uses the cursor parameter and that trim=true yields a lighter response, which hints at when to set those options. There is no explicit statement of when to call this versus the other Pinterest tools, nor any prerequisites or exclusions, leaving the selection decision to the agent.

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