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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety and determinism are covered. The description adds one genuinely useful behavioral fact — that boards belong to a connected Pinterest account, implying an account-linking prerequisite — but says nothing about rate limits, pagination, or what happens if the account isn't connected.

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?

A single front-loaded sentence with no filler; the resource is stated before the provenance note. It is efficient, though its brevity is partly under-specification rather than pure economy.

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 one-parameter read-only list tool with no output schema, the definition is minimally viable but leaves the agent guessing about the return shape — notably whether board IDs usable by a pinning/composing flow are included. The connected-account prerequisite is mentioned, which is the most important missing piece, but the rest is thin.

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 0% for the single accountId parameter, so the schema provides no meaning. The description partially compensates by framing it as 'a connected Pinterest account,' but does not clarify whether accountId is an internal account identifier or a Pinterest user handle, nor where to obtain it.

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 names a specific resource (boards) restricted to a connected Pinterest account, which reads as a retrieval/list operation and clearly distinguishes it from the write-oriented siblings like create_post or publish_post. The verb is implied rather than stated, so it falls just short of a 5.

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 parenthetical '(used by the composer UI)' notes where the data is consumed but gives the agent no when-to-use guidance, no prerequisites (must the account be connected first?), and no comparison to alternatives such as tiktok_creator_info or get_accounts. Context is hinted at, not stated.

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