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

Annotations already cover readOnly and openWorld, so the description's job is to add beyond that — it does so with the credit cost and the cursor-chaining behavior, which the agent cannot infer from structured fields. It stops short of saying what happens on an invalid or private board URL.

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?

Four short sentences, front-loaded with the resource and return payload. The opening 'Board and its pins.' largely restates the title, a small redundancy, but nothing else is wasted.

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 does the necessary work of describing the return shape ('board metadata plus a page of its pins'). What's missing is minor for a read-only retrieval tool: the undocumented cache_max_age parameter and edge-case behavior.

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%: url has an example and cursor is labeled 'Bookmark from the previous response'. The description reinforces the cursor's purpose (paging through the board) but adds nothing for cache_max_age, which is undocumented in both places.

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-object scope: board metadata plus a page of that board's pins. That cleanly distinguishes it from pinterest_pin (single pin) and pinterest_search, though it never names those siblings explicitly.

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 pagination instruction ('Pass the cursor from the previous response') implies the when-and-how of repeated calls, but there is no explicit guidance on when to choose this over pinterest_userBoards or pinterest_search, and no stated failure conditions.

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