List Pinterest boards

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description still adds non-obvious context the annotations cannot convey: zero credit cost and the mandatory connection prerequisite. It stops short of describing pagination or board-count limits, which keeps it from a 5.

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 dense sentences, each carrying independent load: what is returned, when/why to call it with the user-pick rule, and the precondition plus cost. Front-loaded with the outcome, no filler.

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?

No output schema exists, so the description correctly enumerates the returned fields. For a zero-required-parameter list tool embedded in a larger posting workflow, the workflow ordering, cost, and auth prerequisite are all the agent needs.

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 single privacy enum is fully documented in the schema itself (including its default). The description never mentions the privacy filter, so it adds nothing over the schema — the baseline of 3 is appropriate.

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 (List) and resource (Pinterest boards) plus the exact fields returned (id, name, privacy, pin count), so the agent knows what it gets back. It also implicitly distinguishes itself from the write-side sibling post_to_pinterest by being the read step that precedes it.

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?

Gives an explicit ordering rule ('ALWAYS call this before post_to_pinterest'), an explicit reason, and a hard behavioral constraint ('let the USER pick ... Hermoso never chooses one for them'). The prerequisite is also spelled out (Pinterest connected via Settings > Connectors > Pinterest), leaving nothing to inference.

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