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

With no annotations provided, the description carries the behavioral disclosure burden and does so well: it discloses per-result credit cost, approximate total cost, that empty results and failures are not charged, and that cache=true provides a free 24-hour hit while the default is a fresh fetch. This goes beyond a simple read-only statement.

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 description is compact and front-loaded with the resource and output fields. The only minor issue is redundancy around credit cost: '~0.5 credits/pin' and '~13 credits (0.5/result)' restate the same per-result pricing information.

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?

Given the detailed input schema and no output schema, the description is mostly complete: it names the core returned fields, explains costs and cache behavior, and the schema handles pagination, limits, and URL constraints. A small gap is the lack of explicit sibling-tool routing, but an agent can still invoke this tool correctly.

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 the schema already documents url, cache, limit, and cursor in detail. The description reinforces the cache behavior and per-result billing, but it does not add significant parameter-level meaning beyond what the schema provides. Baseline 3 applies.

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 description clearly identifies the resource as pins on a Pinterest board and names the key returned fields (saves, imageOriginal, destinationUrl, top-level author). It lacks an explicit verb like 'list' or 'fetch' and does not distinguish itself from sibling tools such as pinterest_user_pins, but the intent is unambiguous.

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?

The description implies usage for Pinterest board scraping through its name and content, and the URL parameter schema reinforces what kind of URL is valid. However, it never explicitly states when to choose this tool over alternatives like pinterest_pin_details, pinterest_search, or pinterest_user_boards.

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