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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: the chosen board becomes the brand's remembered default and publishes using it surface a `defaultBoardApplied` flag, plus it discloses the underlying GET endpoint and the pinterest.boardId linkage.

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?

Three compact sentences with zero filler; the read-only marker, the scope, the downstream usage, and the default-board behavior are all front-loaded and each carries distinct 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?

For a single-optional-param read tool with no output schema, the description supplies the key operational context an agent needs (board id reuse, required board, default behavior). It stops short of describing the shape of returned board records, but the annotation and schema carry most remaining weight.

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 100%, so brandId is fully documented in the schema, establishing a baseline of 3. The description never mentions brandId, but it does add semantic context about how the returned board id is consumed downstream.

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 opens with '[read-only] Boards of the Pinterest account(s) a brand publishes to', which names the resource and its scope clearly, and the title supplies the verb. It distinguishes itself from the sibling list_youtube_playlists by the Pinterest/boards constraint, though the description itself does not use an explicit verb.

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?

It tells the agent the board id is used as `pinterest.boardId` on publish and that a board is required, which implies the tool is a prerequisite step before publishing. It does not say when NOT to use it or name alternatives for fetching board data, so guidance remains implied rather than explicit.

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